Need help with Hibernate? Read this first:
http://www.hibernate.org/ForumMailingli ... AskForHelp

Hibernate version: 2.1.6

Name and version of the database you are using: Oracle 8i


I have a question about dealing with null values coming from the database. Currently on our setters, we have code to test if the value being set is null and if so, set it to empty string. This has the unwanted side affect of making the object dirty even and causing update statements to fire for read only operations. What is the preferred way to deal with null values coming from the database. We would prefer to not have null checks all over the client code for this. While I realize this problem is independent of hibernate, I thought someone here might have a more elegant way of dealing with this dreaded scenario.

Thanks in Advance.
Mike

What if you instead put the null check on the getter, and then have hibernate use attribute-level access? (I'm not advocating this as a solution, though.)

What if you move your null checks to your getter methods ? Does that have the same side effect of making the object dirty ?

This is a FAQ. You use a UserType.