Andrea, I can't reproduce this. Can you please send me more detailed info.
> On Sunday 20 October 2002 11:49, Gavin King wrote:
> > The reason it doesn't check list!=null is that find() is never supposed
to
> > return a null list How did you make that happen?? Do you have a
> > stacktrace, etc
> Apparently everything works fine, but from the postgres log I see that:
> - the deleted object has not been deleted, but its parent_id column
> has been nullified (if I recall properly you said this, because only
> the update has been cascaded, not a delete, so I may expect this);
> - the ot
> Apparently everything works fine, but from the postgres log I see that:
> - the deleted object has not been deleted, but its parent_id column
> has been nullified (if I recall properly you said this, because only
> the update has been cascaded, not a delete, so I may expect this);
Yep, you
The reason it doesn't check list!=null is that find() is never supposed to
return a null list How did you make that happen?? Do you have a
stacktrace, etc?
> I've found a bug that causes a NPE in the Session.delete(String query)
> implementation: if you pass a query that return no objects yo
