On Oct 10, 2007, at 4:13 PM, Klaus Berkling wrote:
On Oct 10, 2007, at 6:48 PM, Klaus Berkling wrote:
Why does WO create such an odd SQL statement:
UPDATE QA SET question = NULL, answer1 = NULL, id_users = ?,
problem = NULL, date_modified = ? WHERE (id = ? AND answer1 = ? AND
answer2 is N
On Oct 10, 2007, at 6:48 PM, Klaus Berkling wrote:
Why does WO create such an odd SQL statement:
UPDATE QA SET question = NULL, answer1 = NULL, id_users = ?,
problem = NULL, date_modified = ? WHERE (id = ? AND answer1 = ? AND
answer2 is NULL AND date_created = ? AND date_modified = ? AND
you've got multiple fields checked to use for locking purposes.
Checking a field for locking means that if some other process changes
a value that EOF has in memory, the update will fail, and you'll get
an exception.
On Oct 10, 2007, at 6:48 PM, Klaus Berkling wrote:
Why does WO create s
Why does WO create such an odd SQL statement:
UPDATE QA SET question = NULL, answer1 = NULL, id_users = ?, problem
= NULL, date_modified = ? WHERE (id = ? AND answer1 = ? AND answer2
is NULL AND date_created = ? AND date_modified = ? AND figure1url is
NULL AND figure2url is NULL AND figure
