Re: [sqlite] commit transaction/savepoints on program crash

[New text /below/ any text you want to quote, please.] On 9 Aug 2010, at 9:09pm, Josh wrote: > Thanks for the answers, but I guess I should have made my question more > clear. I knew that you can commit every sql statement individually, then > the question would be, how can I roll them back? >

Re: [sqlite] commit transaction/savepoints on program crash

Thanks for the answers, but I guess I should have made my question more clear. I knew that you can commit every sql statement individually, then the question would be, how can I roll them back? In other words I'd like something like savepoint and rollback to savepoint, while not loosing the tra

Re: [sqlite] commit transaction/savepoints on program crash

On 9 Aug 2010, at 5:05pm, Josh wrote: > I'm new to the list and had a question. I know the default behavior for > savepoints (or any transactions) is that if they have not been committed, if > the program crashes, they are lost. Is there any way to have them committed > by > default? Basicall

Re: [sqlite] commit transaction/savepoints on program crash

> Is there any way to have them committed by > default? Basically I *only* want the transaction rolled back in case of an > explicit rollback statement, not due to program crash/power failure, etc. Does > anyone know of a way of doing this? You can avoid transaction begin/commit statements, so tha

[sqlite] commit transaction/savepoints on program crash

Hello all, I'm new to the list and had a question. I know the default behavior for savepoints (or any transactions) is that if they have not been committed, if the program crashes, they are lost. Is there any way to have them committed by default? Basically I *only* want the transaction rolled

Re: [sqlite] commit transaction

Mr roushan ali <[EMAIL PROTECTED]> wrote: > Hi All, > we are working on a multi-threaded > application in linux 2.4.20 using sqlite(2.8.13) > database. we use single database handle for all the > threads to access the database and the handle is > protected with mutex. The handle is kept op

[sqlite] commit transaction

Hi All, we are working on a multi-threaded application in linux 2.4.20 using sqlite(2.8.13) database. we use single database handle for all the threads to access the database and the handle is protected with mutex. The handle is kept open for the lifetime of the application. we have kept p