Subject | RE: [firebird-support] firebird and transaction behaviour questions |
---|---|
Author | Zoran |
Post date | 2016-02-23T15:38:55Z |
-----Original Message-----
From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com]
Sent: Tuesday, February 23, 2016 10:14 AM
To: firebird-support@yahoogroups.com
Subject: Re: [firebird-support] firebird and transaction behaviour questions
23.02.2016 16:03, 'Zoran' zoran565@... [firebird-support] wrote:
rows), database should be in a stable state.
Using transactions when not needed (in my opinion - and I am no expert in
Firebird) just add an overhead to the server.
From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com]
Sent: Tuesday, February 23, 2016 10:14 AM
To: firebird-support@yahoogroups.com
Subject: Re: [firebird-support] firebird and transaction behaviour questions
23.02.2016 16:03, 'Zoran' zoran565@... [firebird-support] wrote:
>> Why would you use transaction for select statements?If other clients are using transactions properly (when updating multiple
> For data consistency. People like consistent data in reports.
rows), database should be in a stable state.
Using transactions when not needed (in my opinion - and I am no expert in
Firebird) just add an overhead to the server.
>> No. For ONE row at the time you don't need a transaction. If you areI don't use ODBC. Probably ODBC writers have a good reason :)
>> changing multiple rows, then you do need to wrap it into transaction.
> ODBC standard writers had different opinion.