On 10/19/05 8:01 AM, "Uzo Madujibeya" <uzomadu@xxxxxxxxx> wrote: > Have you guys by any chance investigated using Hibernate as persistence layer > which you can use to interrogate a number of RDBMS? Many of the issue you > mention with specific database usage are handled by hibernate. > > Uzo > > On 19 Oct 2005, at 12:31, Sean Davis wrote: > > > I am not a programmer, but I do use databases and programming in my work. I > > also started with MySQL but started "experimenting" with postgresql about > > 1.5 years ago. After I saw that the database concepts such as foreign keys, > > referential integrity, and stored procedures were more than "things in a > > book" and could be rapidly implemented in practice, I became very interested > > in making the change. Uzo, I totally agree that using a middle layer can ease (or even eliminate) the pain of moving from one database engine to another. One can even rely on the application or middle layer to maintain referential integrity, transaction safety, etc. However, relying on such a middle layer is inherently less robust (in some ways) than using the database engine to enforce referential integrity and transaction safety. That said, I typically write in perl and so use Class::DBI, DBIx::RecordSet, and DBIx::SQLEngine where possible to eliminate some of the tedium associated with dealing directly with SQL and different database engines. As I understand it, Class::DBI is probably most similar to Hibernate, as it treats tables as classes and can discover and capitalize on foreign-key relationships to link the classes. Sean --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|