From: Michael H. <mg...@gm...> - 2011-05-04 20:12:51
|
> Good catch. The problem is that a database disconnect causes > update() calls on the database observers, and the close query handler > fails to notice that the database has already been disconnected (and > the transaction rolled back). The easy thing to do is to just fix > that. But the right thing is to have a disconnect confirmation to be > shown when there are active transactions in SQL editor windows. I'll > look into that. Fix committed to SVN as revision 2115. Thanks -- Michael Hieke |