File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Object Relational Mapping and the fly likes Hibernate vs Legacy DataBases Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Databases » Object Relational Mapping
Bookmark "Hibernate vs Legacy DataBases" Watch "Hibernate vs Legacy DataBases" New topic
Author

Hibernate vs Legacy DataBases

visu nallamaru
Greenhorn

Joined: May 09, 2010
Posts: 15

Can we prefer Hibernate to ease the data base transactions when maintaining/working with legacy databases ?
Paul Sturrock
Bartender

Joined: Apr 14, 2004
Posts: 10336

Not sure I understand your question. Prefer Hibernate to what?


JavaRanch FAQ HowToAskQuestionsOnJavaRanch
visu nallamaru
Greenhorn

Joined: May 09, 2010
Posts: 15

Can we introduce ORM (hibernate ) layer when working with Legacy Database which is directly accessed by JDBC ? what are the complications to look for ?
Paul Sturrock
Bartender

Joined: Apr 14, 2004
Posts: 10336

Yes we can. Hibernate uses JDBC, so as far as the low level connection stuff is concerned there is no difference.The complications depend on the database. By "legacy" I infer poorly modelled. Hibernate is fairly strict when it comes to relational databases that are not actually relational (e.g. entities without primary keys) so there may need to be some compromises made. But Hibernate always allows you to run native SQL, so anything you can currently do on your legacy database in SQL you can carry on doing if you have to.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Hibernate vs Legacy DataBases