Subject | LockSQL |
---|---|
Author | Riho-Rene Ellermaa |
Post date | 2001-10-16T11:03:24Z |
It's hard to get the answer.
When my app gets error "Unable to initialise default LockSQL", then should
I create it myself? I want to disable users possibility to edit the record
from 2 places simultaneously.
Query:
SELECT id,(select account from account a where a.id=dom_pay.accid) as
accountno
, ACCID
, STATUS
, BBANK
...
, VER
, SIGN1
, SIGN2
, BANK
FROM account
join dom_pay on account.id=dom_pay.accid
where uid=:UID and install=:INST
for update
KeyLinks:
ID
ACCID
STATUS
PessimisticLocking=true
Keylinksautodefine =false (was true - same results)
How can I make the IBO4.2Eb to create LockSQL automatically?
Riho-Rene Ellermaa
senior programmer
Hansabank
When my app gets error "Unable to initialise default LockSQL", then should
I create it myself? I want to disable users possibility to edit the record
from 2 places simultaneously.
Query:
SELECT id,(select account from account a where a.id=dom_pay.accid) as
accountno
, ACCID
, STATUS
, BBANK
...
, VER
, SIGN1
, SIGN2
, BANK
FROM account
join dom_pay on account.id=dom_pay.accid
where uid=:UID and install=:INST
for update
KeyLinks:
ID
ACCID
STATUS
PessimisticLocking=true
Keylinksautodefine =false (was true - same results)
How can I make the IBO4.2Eb to create LockSQL automatically?
Riho-Rene Ellermaa
senior programmer
Hansabank