Den 19/08/11 11.34, MANUEL FIDALGO SICILIA skrev:
Dear all,

Foremost, I would like to say that I'm new to the AS/400 world so sorry
if I ask stupid things...

At work we are using v6r1m0 and we would to write some Java programs
using the AS/400 as database.

The problem comes when deciding what persistence engine to use: I can't
see clearly if the AS/400 is relational or non-relational and I would
like to know which should be better JPA or JDO. I know some people use
JPA but I'm wondering if it is not better to use JDO which has support
for both relational and non-relational and if JPA will have performance
problems because it is made for relational.

So what do you think? JDO or JPA? Or maybe just jdbc!
First of all: Will you need to access database data created outside your Java program? If yes, you need to look into reverse modelling creating Java objects from database tables. I believe Hibernate has some facilities for this. It also has a DB2/400 dialect.

Then, most O/R mappers want the database to support commit-rollback for consistency. This may not be enabled for your tables in DB2/400. This is required for e.g. Hibernate to work.

(and The JDBC driver is in the jt400 jar files.)


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.