Re: sql in php with paging

Hey Thorbjørn!

Any particular reason for doing so? I chose the Hibernate path due to the maturity of the Hibernate project, and the available online resources for the underlying engine, but was pleased to see that there was a choice for JPA implementation (which is incredibly important when you need to select a technology which may have to be maintained for many years). The more implementations the less chance for them all to wither :D

Hibernate is part of a framework. That framework works best if you are designing the classes then deriving the data bases to implement them. It works less well the other way around. My opinions may be a little dated. I started using Hibernate and switched to iBatis a couple of years ago for this reason.

Recently I switched from iBatis to Eclipselink. TopLink (the codebase donated to Eclipse upon which Eclipselink is based) has a long history as a commercial product offered by Oracle. I think that it is a better fit when the databases have been established and classes have to be developed to work with databases.



-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Thorbjørn Ravn Andersen
Sent: Tuesday, October 21, 2008 3:16 PM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] sql in php with paging

Blalock, Bill skrev:

Thorbjørn wrote:

I have just finished refreshing my Java knowledge and found that the

Java Persistance Arcitechture (JPA) defined in EJB3 can run on non-J2EE
servers (plain web containers or stand-alone applications) and is very
powerful. It allows for simple paging by setting the "start at" and
"give me X items" on each query, and then letting the persistence layer
deal with asking the database properly.

Let me also suggest looking at Eclipselink implementation of JPA. It is based on the TopLink code base donated by Oracle.

Any particular reason for doing so? I chose the Hibernate path due to
the maturity of the Hibernate project, and the available online
resources for the underlying engine, but was pleased to see that there
was a choice for JPA implementation (which is incredibly important when
you need to select a technology which may have to be maintained for many
years). The more implementations the less chance for them all to wither :D

/Thorbjørn