W
W0lfw00ds
Guest
Lets say we have a procedure which takes in a buffer-parameter:
myprocedure.p:
DEF PARAM BUFFER bufferParameter FOR DatabaseTable.
/* Get the same buffer in EXCLUSIVE-LOCK for updating */
FIND CURRENT bufferParameter EXCLUSIVE-LOCK.
/* Update the value */
ASSIGN bufferParameter.MyField = "new value".
/* Reset the locking mode back to the original one? */
FIND CURRENT bufferParameter NO-LOCK.
The problem with this approach is that it is possibly changing the original locking-mode of the passed buffer parameter. It is possible that the buffer was in EXCLUSIVE-LOCK or f.ex in NO-LOCK. By changing the locking-mode, this procedure could invoke updating errors in some other programs using this same buffer.
Another solution would be to create a new temporary buffer for the same table, and then update the database thru that buffer (without touching the passed parameter buffer). The con of this approach is that the original passed buffer parameter will become 'out-of-date'. It would require a new database query to update it's 'MyField' value to match the one in the database.
How I could reset the buffer's locking-mode back to the original one after updating it's fields?
Continue reading...
myprocedure.p:
DEF PARAM BUFFER bufferParameter FOR DatabaseTable.
/* Get the same buffer in EXCLUSIVE-LOCK for updating */
FIND CURRENT bufferParameter EXCLUSIVE-LOCK.
/* Update the value */
ASSIGN bufferParameter.MyField = "new value".
/* Reset the locking mode back to the original one? */
FIND CURRENT bufferParameter NO-LOCK.
The problem with this approach is that it is possibly changing the original locking-mode of the passed buffer parameter. It is possible that the buffer was in EXCLUSIVE-LOCK or f.ex in NO-LOCK. By changing the locking-mode, this procedure could invoke updating errors in some other programs using this same buffer.
Another solution would be to create a new temporary buffer for the same table, and then update the database thru that buffer (without touching the passed parameter buffer). The con of this approach is that the original passed buffer parameter will become 'out-of-date'. It would require a new database query to update it's 'MyField' value to match the one in the database.
How I could reset the buffer's locking-mode back to the original one after updating it's fields?
Continue reading...