I am unable to compare dates in MySQL queries. I'm trying to get all rows newer than a certain date by comparing the theDate column to a passed in parameter. I've tried explicitly stating the type in the mapping file with no luck. I was able to similarly compare integer fields, so I can't be too far off.

I keep getting the following error:

net.sf.hibernate.ObjectNotFoundException: No row with the given identifier exists: 9, of class: com.mypackage.OtherClass

Perhaps there's a mapping error, but why would it give me an object not found error on a completely different class than the one I'm querying?

Here's more info:

from persisted bean class (called Bean)

private Date theDate;

from mapping file:

<property name="theDate"/>

GregorianCalendar cal = new GregorianCalendar();
cal.set(2003,1,1);
StringBuffer buffer = new StringBuffer("select bean from Bean bean where (bean.theDate) > :aDate");

... later ...

Query q = session.createQuery(buffer.toString());
q.setDate("aDate",cal.getTime());
results = q.list();

Any help appreciated!

I susspect you have an association mapped somewhere, where the foreign key constraint is not statisfied.

[quote="gloeglm"]I susspect you have an association mapped somewhere, where the foreign key constraint is not statisfied.[/quote]

What's weird is that I'm able to compare an Integer attribute of the same class without problems.

Are you really loading exactly the same object(s) with both queries?

[quote="gloeglm"]Are you really loading exactly the same object(s) with both queries?[/quote]

yeah, I just replaced the Date with an Integer attribute:

StringBuffer buffer = new StringBuffer("select bean from Bean bean where (bean.theInt) > :aInt");

... later ...

Query q = session.createQuery(buffer.toString());
q.setInteger("aInt",5);
results = q.list();

Yes, but do they refer to exaclty the same row in your database?

[quote="gloeglm"]Yes, but do they refer to exaclty the same row in your database?[/quote]

I played around some more, getting the Integer and Date comparison set up to return the same row, and have never seen the problem since (even with the original query that was causing the problem). I cannot explain why the problem occurred in the first place or why it is no longer happening, but I thank you for trying to help me out!