Subject | Transaction and time keepping program |
---|---|
Author | Frank Wang |
Post date | 2002-02-13T00:15:14Z |
Hi,
I know we have to keep transaction open as short as possible,
here is a simple situation I'd like to ask gurus here about a proper
management of transaction:
A time keepping program runs 24 hours a day to capture
time in/out of workers, when user swipes his card, the program
has to verify a IB server to see if he is a valid user before inserting
the record to a text file, if we keep a transaction open for validating
purpose, things are simple but the transaction will be opened all the
time. if we start the transaction to verify , rollback afterward, this
has to be done for every swipe which seems an expensive operation,
any idea?
Also, what does the 'Oldest transaction' mean? thanks.
Regards,
Frank
I know we have to keep transaction open as short as possible,
here is a simple situation I'd like to ask gurus here about a proper
management of transaction:
A time keepping program runs 24 hours a day to capture
time in/out of workers, when user swipes his card, the program
has to verify a IB server to see if he is a valid user before inserting
the record to a text file, if we keep a transaction open for validating
purpose, things are simple but the transaction will be opened all the
time. if we start the transaction to verify , rollback afterward, this
has to be done for every swipe which seems an expensive operation,
any idea?
Also, what does the 'Oldest transaction' mean? thanks.
Regards,
Frank