• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Liutauras Vilda
Sheriffs:
  • Rob Spoor
  • Junilu Lacar
  • paul wheaton
Saloon Keepers:
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Carey Brown
  • Scott Selikoff
Bartenders:
  • Piet Souris
  • Jj Roberts
  • fred rosenberger

When not to use an ORM tool

 
Ranch Hand
Posts: 226
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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?
 
Ranch Hand
Posts: 2676
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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 ]
reply
    Bookmark Topic Watch Topic
  • New Topic