Thank you very much for this reply which is maximally informative.
>I think there'd be a problem if you had a "locked" field in the db; what
>if a record was locked, and James got restarted (or the machine died and
>assuming that the db was on a different machine). When James got
>resurrected, the record would be still in the locked status;
The "locked" field would just be a text field, like any other text field,
telling the retriever/examiner of the record that the message was "locked"
whatever that means. The message could be taken off the db on the basis of
some other information at any time [after a crash, before a crash...], such
as the age of the record, at any time because the "locked" field would have
no *meaning* to the db.
But I may be missing something.
The field:
>| message_state | varchar(30) | | |
intrigues me. Does it tell whether the message is locked? I am
undoubtedly on a tangent here, but I still recommend using SQL directly.
John
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
