If the framework is designed to do it all starting from scratch - like
Rails if I understand it correctly - then it makes perfect sense that Rails
owns it.

Which in the end is really to bad because it can mean that Rails doesn't
live in the reality of the a DBA's existence (i.e. more geared towards shops
that don't have a "full" staff). In my short stint with RoR I loved the
fact that they tried to make the programmer productive by giving you stuff
"for free" and then you could easily implement your own functionality to
override/extend the default if you wanted to. I hope to have similar
features in RPGUI.

If you want to use it the other way around you must use a tool to create a
bean that corresponds to the database table so Hibernate is happy

I had the luxury of creating the tables from scratch so most of my stuff
worked out of the box, but even then I had issues because I didn't have a
full understanding of the ORM framework before I started using it. In the
end the issue I had with Hibernate wasn't with it's XML mapping or Abstract
bean creation, but instead how the runtime API forced your tables to be
authored a certain way (i.e. doing a JOIN was a *pain* if the joining
columns weren't named the same - is that fixed in latter versions?).

Aaron Bartell
www.SoftwareSavesLives.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

This mailing list archive is Copyright 1997-2024 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.