User locks are handled totally on the application side as long term

cooperative locks which may extend beyond the normal transaction boundaries.

Their purpose is to indicate to an application that someone is `working'

on an item. So it is possible to putan user lock on a tuple's oid,

on an item. So it is possible to puta user lock on a tuple's oid,

retrieve the tuple, work on it for an hour and then update it and remove

the lock. While the lock is active other clients can still read and write

the tuple but they can be aware that it has been locked at the application

LOCALE_NAME_MAX_LENGTH);

ret_val=GetLocaleInfoEx(wc_locale_name,LOCALE_SNAME, (LPWSTR)&buffer,

#defineAttrNumberIsForUserDefinedAttr(attributeNumber) \

((bool) ((attributeNumber) > 0))