These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 
Author Message
 Post subject: DOA or not DAO this is the question?
PostPosted: Wed Jul 18, 2007 11:41 am 
Regular
Regular

Joined: Wed May 02, 2007 2:42 pm
Posts: 101
Hey,

One of the greatest things in hibernate that you dont need to deal with DB.

you are wotrking with object, like without the need to be aware to the DB,

but this is not exactly true.

For exmaple :

I have User with OneToOne to City.

In simple java code if i want to delete city all i need to do is:

city = null;

but in hibernate this is not enough. You need to delete all the reference to city, so you can not write just java code without the need to be aware to the ORM layer.

I thought to solve it by forbid to use in set null and obligant the developer to use in DAO for operations like this.

How do you guys solve issues like this?

Thank you


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.