Hi guys! I've been studying hibernate again since we're not being given any task as of the moment. Most tutorials on ORM would give an example of how to map a class member to a database table field. But this is easy if you're doing everything from the ground up. What if there is an already existing database? Would it be as comfortable to map your objects as you would do when you start from zero? Thanks!

Hi lamia,

Of course nothing beats a ground up design, since you won't be thinking about the legacy designs and maybe you will jsut compromise minimally. The good thing about Hibernate/NHibernate is that it lets you abstract the data model and the object model, whether the data model is legacy design or existing; hibernate/nHibernate itself leaning to an OOP approach to data access.

Kind of remind me of this thread:http://msforums.ph/forums/thread/191606.aspx

naku kung legacy and badly designed database yan, ang hirap i-map sa objects. malamang yan pati objects mo susunod sa pagkaka-lay out ng db, kaya pati objects mo sasama ang itsura.

pag ganyan, i will insist on handwritten O/RM. i won't use Hibernate or any other object/db mapper.