transaction.commit() is this necessary if we didn't do any data manipulation on database?

Hello

I'm just wondering, if do we still need to invoke commit even though we only executed a select query (which means no manipulation will happen on database)?
On the other hand, or is it efficient to call commit without doing any manipulation on database?

Thanks

A select query does not need a commit.

You can set a connection to auto commit or set method level transactions or some other form of transaction level management to take care of commits

Thank you Deepak for your quick response,

Another question, sorry i just thought of this, if we don't need to commit.. should we need to begin a transaction?

Since you do not want a commit you do not need to start a transaction

Deepak Bala wrote:A select query does not need a commit.

You can set a connection to auto commit or set method level transactions or some other form of transaction level management to take care of commits

Largely correct. However, most databases will have to rely on their time out behvaiour to release the resources associated with the transaction if you don't commit or rollback. So if you start one, its a good idea to finish it. Like you said, the best approach for selects is not to use a transaction.

Point taken, plus it will surely reduce the amount of overhead without using transaction in a select query, Thank you for your immediate response guys.

Ryann,
That's if you really don't have a transaction. Most drivers give you a one statement transaction if you don't already have one.

Thanks Jeanne, i will check on the driver that i am using if it needs to,