I really don't know where to ask this, so I am trying here because someone
may have encountered a similar problem...
I use MSSQLServer 2000 and JTurbo (JDBC 2.1) driver.
Wicket 1.3, Databinder 1.1
I ran into a case where my tables had triggers on them. Hibernate wouldn't
let the update occur
I was able to narrow the problem scope a little.
The difference is between getting a result from a Criteria object vs
Session.load().
With both drivers, using the criteria object gets a fully populated object
(with children)
With the JTurbo (JDBC 2.1) driver, Session.load returns the fully
If you have lazy-loaded objects in your graph then they are initially
populated with Hibernate proxies and only resolved from the database
when you access them in your application code. I imagine that in one
case the Hibernate transaction is being closed before you have walked
the object graph
Scott Swank wrote:
If you have lazy-loaded objects in your graph then they are initially
populated with Hibernate proxies and only resolved from the database
when you access them in your application code. I imagine that in one
case the Hibernate transaction is being closed before you have
you do know that session.load() will return a proxy even if the object
doesnt exist, where as session.get() will return null.
-igor
On 3/9/07, ChuckDeal [EMAIL PROTECTED] wrote:
Scott Swank wrote:
If you have lazy-loaded objects in your graph then they are initially
populated with
igor.vaynberg wrote:
you do know that session.load() will return a proxy even if the object
doesnt exist, where as session.get() will return null.
-igor
Yeah, but that really doesn't apply to this sceanrio. I KNOW that there is
data. I KNOW that with either driver, when I use a
I'd look for something like auto-commit inserting itself between these
two lines.
result = (SpecChangeModelObject) criteria.uniqueResult();
assertNotNull(SpecChangeModelObject should not be null, result);
but that's just my best guess.
Scott
