Subject | Re: [ib-support] Serialization? |
---|---|
Author | Raul Chirea |
Post date | 2002-07-06T20:22:07Z |
Hi,
From: "Matteo Giacomazzi" <matteo.giacomazzi@...>
However, it has table level locking also but this is not the default
behaviour !
transactions types and properties.
Regards !
Raul.
From: "Matteo Giacomazzi" <matteo.giacomazzi@...>
> I meant "procedure" in a "workflow" environment! :)Good !
> That is: the sequence of operations performed to accomplish a task! :)
> Well, if the server keep blocked only clients that would insert theIB/FB has row level locking support, so it locks only that rows that ... !
> same rows, there's no problem.
However, it has table level locking also but this is not the default
behaviour !
> I wonder if the server keep blocked all the clients that want toDon't wary about it if not using table level locking !
> perform an INSERT into the same table: this one could be a problem!
> Because the server would allow only one client per time to perform a
> download and this thing will compromise any kind of parallel download.
> Maybe the default transaction option "SNAPSHOT" means that only theWrong ! Read API guide - transactions chapter ! It will bring some light on
> "same rows" are taken under control?
transactions types and properties.
Regards !
Raul.