It sounds like the design of the software is the issue. It needs to not
keep a transaction open for so long. Can you not use transactions and
just use auto commit to commit after every statement? If a nasty
workaround is what you are after :)
On 5/09/2012 7:39 PM, Radha Krishna wrote:
Thanks for your reply. Do we have any other workaround to suggest to
customer? We can't just upgrade now in the customer setup. Some kind
of workaround is required.
On Tue, Sep 4, 2012 at 12:04 AM, Thomas Mueller
<[email protected] <mailto:[email protected]>>
wrote:
Hi,
Please don't send emails to me directly.
We can't upgrade to latest version
In any case you will have ensure that the transaction is not kept
open for such a long time.
We would like to apply workaround of disabling transaction log
in the customer scenario using "LOG=0". Is this correct
workaround? Will it have any impact?
It is not a correct workaround, and it will make the database
unreliable, as documented in the FAQ:
http://h2database.com/html/faq.html#reliable
Also I understand that there is no transaction log at all in
the latest version. Is that right?
No, that's not correct. The latest version does have a transaction
log, but not as a separate file. The transaction log is now
included in the database file.
Regards,
Thomas
--
You received this message because you are subscribed to the Google
Groups "H2 Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
