Sirs/Madams,

What's the proper way to allow a user to cancel a long-running query initiated by Query.list()? I tried Session.close() from a separate thread, but it complains quite loudly. According to the docs, the session implementation is not likely to be thread-safe. Sooo... how can i have one thread running a query and another thread come along and cancel the query?

Thanks,
Jeff

Hmmmm this is very interesting. No-one ever asked for this before. I never thought about it, 'cos its not something you can do in a web application.

So we need a Query.cancel() method? Hummm ... oh kah ....

Add it to JIRA.

For now, use Query.setTimeout()

Done. Thanks, gavin.

BTW, i think we're doing a *lot* of things not anticipated... and it's holding up really well. The biggest difficulty is in getting my DBAs to be happy about us (the java team) using Hibernate. They lose sleep when apps don't access the data through stored procedures, and can't stand the idea that their precious database is treated like a "storage tank" ;]

Anyway, thanks again.

I have implemented this as Session.cancelQuery(). Probably commit it later today. Useful, I think.

By default, any person is loosing sleep when another person is doing something that makes said person less important/critical ;-) It get's annoying when stupid architechture decisions have to be made because of such people :-|

Strangely enough, we are not out to make data people redundant here. In fact, doing Hibernate has given me a much better appreciation for what DBAs and data modellers actually do. What we are really trying to do is let them get back to doing what they do well, instead of what we do well (ie. write code).