Thank you very much. 2 vs 1, but in this case I asume that Dmitry wins.
I'll check the optimized configuration files.
Jaume
2014-07-07 20:41 GMT+02:00 Dmitry Yemanov dim...@users.sourceforge.net
[firebird-support] firebird-support@yahoogroups.com:
07.07.2014 21:14, Thomas Steinmaurer
Hi,
Ï am not sure that Dmitry wins here, since original question is not 100%
correct.
Cache is always per server process - each server process has own cache,
in all architectures, and difference is in connection/server process model.
So, SuperClassic is like Classic in terms of usage - the
08.07.2014 15:07, Alexey Kovyazin wrote:
Ï am not sure that Dmitry wins here, since original question is not 100%
correct.
Cache is always per server process - each server process has own cache,
in all architectures, and difference is in connection/server process model.
Not really correct
Hi!
I have Firebird 2.x database which from time to time has rather long
transactions - up to 30 seconds and so, there is high probability that the same
record will be updated from the several different transactions and the lock
conflict - deadlock exeption will be raised. I am currently using
On Jul 8, 2014, at 3:37 PM, jonatan.laurit...@yahoo.dk [firebird-support]
firebird-support@yahoogroups.com wrote:
I have Firebird 2.x database which from time to time has rather long
transactions - up to 30 seconds and so, there is high probability that the
same record will be updated
Not to make you jealous or anything, but we just came back into cell
phone range o n our leisurely cruise down the Maine coast. I'd send a
picture, but the list won't let me. Now it's 6:30. The drinks flag is
out; the dog has had her run through the woods and a bit of swimming.
Life is
