Hugo wrote:

>
> I'm executing a "long duration" Stored Procedure which includes an
> UPDATE TABLE SET FIELD1=value .
> I must wait until StoredProcedure finish, to automatically commit
> transaction to server, and meanwhile I can't post any other changes to
> table TABLE, even in other fields than FIELD1.
> Is this the current behavior? Or is there a way to lock ONLY that field I
> need to update inside the Stored Procedure?

No. And there never will be. Remember - this is an RDBMS. We are talking sets
here. Each row is a set and as such each column is an attribute of that set.
Changing a column implies changing the set. If the column you are changing
doesn't belong to the set move it to another table.

Where were you trying to get to before you locked yourself into this particular
corner?


Paul
--

Paul Reeves
http://www.ibphoenix.com
taking InterBase further