Subject | Re: Design problem |
---|---|
Author | Alexander V.Nevsky |
Post date | 2003-06-23T13:50:45Z |
--- In firebird-support@yahoogroups.com, "Dimitry Sibiryakov"
inserts if it's triggers don't make non-incremental updates of another
tables, but about updates - it depends. If we make incremental update
like "Set Column=Column+:Param" - yes. If "Set Column=:Param" - I
prefer to get lock conflict if record was changed and commited since I
started transaction and use concurrency.
Best regards, Alexander.
> Only report transactions that need serializable read. Update/insertDimitry, I prefer to not so categorical on this. I can suggest about
> transactions may be (and should be) "read commited".
inserts if it's triggers don't make non-incremental updates of another
tables, but about updates - it depends. If we make incremental update
like "Set Column=Column+:Param" - yes. If "Set Column=:Param" - I
prefer to get lock conflict if record was changed and commited since I
started transaction and use concurrency.
Best regards, Alexander.