Re: HELP: Long (lasting) transactions?

In article <3makt8$sv@hustle.rahul.net> billb@lore.kla.com "Bill Baloglu" writes: > ... there will be scenarios > under which a database transaction may be open for a few > days ... This would certainly cause problems with the database product we use (ADABAS), where there are timeout limits on transactions. The principle we use here is that programs should only rely on the database locking mechanisms for short term locking. If there is a transaction which could last for a long time, then programs should be coded to handle it explicitly - e.g. by setting a 'locking flag' somwehere, or using an incrementing version number on the record. This means your code is fully portable, and you are in control over what happens if there is contention - how long a user is kept waiting, which user sees the error, what the error message is, etc. John +---------------------+------------------------------------------------------+ John P.McCreesh | Internet: jpmccreesh@pines.demon.co.uk Forbo-Lancaster Ltd. | X.400: c=GB,a=CWMAIL,p=FORBO,g=John,s=McCreesh Lancaster, England | Voice: +44 (0) 1524 65222 Fax: +44 (0) 524 61638