Subject | Transactions question (another) |
---|---|
Author | Michael Vilhelmsen |
Post date | 2004-04-01T11:13:30Z |
Hi
When I start an aplication and when it has started all up, then I end
i normally.
When starting the appl. I read some tables.
Before every read I do a some reads.
After each read I do a commit.
When shutting down, I do some reads and some update.
After each update / read I do a commit.
Before I start my appl. my oldest active transaction is 1763 and next
transaction is 1764.
After I shut down my appl. oldest active is 1767 and next transaction
is 1772.
This will be like this until the next time I connect to the DB (from
any machine on LAN).
Then the oldest active is 1781 and next transaction is 1782.
Is this normal or do I do sometehing wrong ?
It seems to me, that the DB doesn't update thise information, until
someone read, insert or deletes from the DB.
I have been very carefull to do a commit after each insert / update,
and also if I close a windows, I commit any active transactions.
Regards
Michael
When I start an aplication and when it has started all up, then I end
i normally.
When starting the appl. I read some tables.
Before every read I do a some reads.
After each read I do a commit.
When shutting down, I do some reads and some update.
After each update / read I do a commit.
Before I start my appl. my oldest active transaction is 1763 and next
transaction is 1764.
After I shut down my appl. oldest active is 1767 and next transaction
is 1772.
This will be like this until the next time I connect to the DB (from
any machine on LAN).
Then the oldest active is 1781 and next transaction is 1782.
Is this normal or do I do sometehing wrong ?
It seems to me, that the DB doesn't update thise information, until
someone read, insert or deletes from the DB.
I have been very carefull to do a commit after each insert / update,
and also if I close a windows, I commit any active transactions.
Regards
Michael