>No problem really, all it means is the application has issued a start of transaction command, it just isnt doing anything at the moment.
>Transactions allow any data added during the applications running to be rolled back should, for example, the application crash itll prevent half-written data remaining >stale in your database.
>My guess is when you Exit the application correctly, itll issue a COMMIT statement to store the transactional data to your database.
Ok Andy, but what if I do an UPDATE operation on the database within this transaction, it will acquire exclusivelock on that table and will release only at the commit (or rollback) of this transaction, is that right?? So, if this transaction only finishes with the exit of the application the UPDATE operation will cause a lot of locks and deadlocks, won't they???
