File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Object Relational Mapping and the fly likes When not to use an ORM tool Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Databases » Object Relational Mapping
Bookmark "When not to use an ORM tool" Watch "When not to use an ORM tool" New topic

When not to use an ORM tool

Tonny Tssagovic
Ranch Hand

Joined: Dec 30, 2003
Posts: 226
Hello guys,
I have never used an ORM tool before, but have followed some discussions on several forums about JDO spec. and ORM tools, and why they r so cool alternatives to Entity EJBs.
Now Assuming I have a new project (so there is initially no existing DB) when should I stick to Relational DBs and not use these alternatives. (Also assuming that learning a new tool is not a big deal)??
Any comments?
Matthew Phillips
Ranch Hand

Joined: Mar 09, 2001
Posts: 2676
In my opinion it is probably too early to make that decision on a new project. My recommendation would be to write your code in such a way that when it comes time to make the persistence decision, you will be open to either. You may find that much of the code that you will need to write to achieve the project's persistence needs has already been written for you in one of the ORM tools.
[ February 25, 2004: Message edited by: Matthew Phillips ]

Matthew Phillips
I agree. Here's the link:
subject: When not to use an ORM tool
It's not a secret anymore!