Query throws "object references unsaved transient insta

PaulRivers · **Joined:** Sat Nov 25, 2006 2:56 pm **Posts:** 11

I have this code:

Code:

Query query = session.createQuery("from Choice where text = :choiceText");
query.setString("choiceText", choice.getText());
Choice dbChoice = (Choice) query.uniqueResult();

And I get this exception:

Quote:

Exception in thread "main" org.hibernate.TransientObjectException: object references an unsaved transient instance - save the transient instance before flushing: aftectest.Choice

Has anyone else seen this? This makes absolutely no sense to me - the exception seems to be saying that the Query object itself is referencing an unsaved transient instance...which doesn't make any sense because how it retrieve a unsaved object by doing a query against the database?

PaulRivers · **Joined:** Sat Nov 25, 2006 2:56 pm **Posts:** 11

P.S. It doesn't matter whether I do query.uniqueResult() or query.list(), I get the same exception either way.

LaLiLuna · **Posted:** Sat Dec 16, 2006 5:15 pm

You should consider to do what is indicated in the input form:

post mapping, classes, the source code calling the class. In addition a full stacktrace does help to indicate the root of the problem.

PaulRivers · **Joined:** Sat Nov 25, 2006 2:56 pm **Posts:** 11

It appears that some other unrelated database stuff is being done when I do the query call, and that other stuff is causing the exception.

rajasaur · **Joined:** Tue Aug 23, 2005 8:52 am **Posts:** 181

If the object you are retrieving hasnt been committed yet (in the same tx but not yet saved) or if it references a collection thats not saved it, the exception that you indicate below might appear. If you have any other unsaved objects in the same Transaction, consider saving those before calling the Query.

PaulRivers · **Joined:** Sat Nov 25, 2006 2:56 pm **Posts:** 11

I'm completely familiar with saving objects before adding them to certain collections.

At the moment, I'm thinking this error happens because I was trying to add one object to two different collections, which isn't allowed with a one-to-many collection mapping. I know the error message doesn't make sense, but that's the only thing I can come up with.

Now I'm trying to do a many-to-many mapping, but unlike the examples which work perfectly, my mapping end up with a "must have same number of columns" error. *sigh* But that's a different problem...