Hi Igor, I'm quite sure I did not. By the way, I even tried the following
code (that should BEGIN and COMMIT changes), but result is the same.
char * errors;
sqlite3_exec( waypoint_db, "BEGIN", 0, 0, 0 );
int ret = sqlite3_exec( waypoint_db, sqlstring, 0, 0, &errors );
while( ret != SQLITE_OK )
{
printf("There is some errors while executing SQL statement:\n ");
sqlite3_free( errors );
ret = sqlite3_exec( waypoint_db, sqlstring, 0, 0, &errors );
}
sqlite3_exec( waypoint_db, "COMMIT", 0, 0, 0 );
sqlite3_exec( waypoint_db, "END", 0, 0, 0 );
Igor Tandetnik wrote:
>
> papillon <[EMAIL PROTECTED]> wrote:
>> I update a record with the following code:
>>
>> rc = sqlite3_exec(waypoint_db, sqlstring, callback, 0, &zErrMsg);
>>
>> function return SQLITE_OK.
>>
>> I use a SELECT to see the records and yes, the above records seems to
>> be updated, it shows the new value.
>>
>> I quit the application (correctly closing the db), open it again and
>> ... the record is showing the value prior to the update call.
>> So it seems that even if a SELECT statement show that the value has
>> been changed, these updates are not committed to disk ?
>
> Have you, by any chance, started a transaction (with BEGIN statement)
> but then closed the connection without committing it? This is equivalent
> to rolling it back.
>
> Igor Tandetnik
>
>
> -----------------------------------------------------------------------------
> To unsubscribe, send email to [EMAIL PROTECTED]
> -----------------------------------------------------------------------------
>
>
>
--
View this message in context:
http://www.nabble.com/Odd-behaviour-on-UPDATE-tf4787954.html#a13697511
Sent from the SQLite mailing list archive at Nabble.com.
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
