Is it possible to conditionally suppress the “commit transaction” question when exiting the solution? I suspect what’s needed here is a means for Servoy to send an instruction to the backend to suppress the commit question. Possible? I’m using the bundled Sybase ASA database.
I’m in the process of preparing a live demonstration of my solution. If the user logs on as “demo” a transaction is started. On quitting the solution I’d like to suppress the option to commit the transaction.
Why don’t you roll back the transaction when the solution is closed ?
Then you won’t get a message that it has open transactions and you undo all changes that the demo user made.
Isn’t that what you intended to do ?
Hope this helps.
ROCLASI:
Why don’t you roll back the transaction when the solution is closed ?
Then you won’t get a message that it has open transactions and you undo all changes that the demo user made.
Isn’t that what you intended to do ?Hope this helps.
No, no, no, no!!! That would be too easy, too obvious! Yes, that’s exactly what I need, intend and will do. Thanks, Robert.
if someone kills the client (the hard way) so the close method is never fired, what will happen to the open transaction?
It will rest in peace
HJK:
if someone kills the client (the hard way) so the close method is never fired, what will happen to the open transaction?
what would make most sense considering the data state of the client is unknown at the moment of the crash?
jaleman:
HJK:
if someone kills the client (the hard way) so the close method is never fired, what will happen to the open transaction?what would make most sense considering the data state of the client is unknown at the moment of the crash?
I’d rather roll back the transaction. Preserve the data.
Personally I have only a couple of places where I invoke transactions.
Morley:
jaleman:
HJK:
if someone kills the client (the hard way) so the close method is never fired, what will happen to the open transaction?what would make most sense considering the data state of the client is unknown at the moment of the crash?
I’d rather roll back the transaction. Preserve the data.
And that is exactly what Servoy does. After the timeout (the server waits a bit as you could also suffer from a bad connection) the client is cleaned up and open transactions are rolled back.