Re: [sqlite] Dropping updates after exiting application

[Will Leshner]

On 6/4/07, Omar Eljumaily <[EMAIL PROTECTED]> wrote:


qlite3_prepare_v2(con->_db, text.c_str(), text.size(),  &_stmt, &tail);
sqlite3_bind_text(_stmt, which, s.c_str(), s.size(), SQLITE_TRANSIENT);
sqlite3_step(_stmt);


Is one step enough to finish the operation?

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

[sqlite] Dropping updates after exiting application

[Omar Eljumaily]

I have this problem where my application is is dropping updates after 
exiting my application.


create mytable
{
int id primary key,
name text
};

Something like:

"insert into mytable(name) values('myname')"

would update properly.

However

"update mytable set name = 'newname' where id = 1"

would propogate for the life of the application, then disappear after 
the app exits.


I've checked the autocommit state and that's set to 1.

I'm using roughly:

qlite3_prepare_v2(con->_db, text.c_str(), text.size(),  &_stmt, &tail);
sqlite3_bind_text(_stmt, which, s.c_str(), s.size(), SQLITE_TRANSIENT);
sqlite3_step(_stmt);

If I view the file in sqlite3.exe, I don't see the changes.  The update 
changes only appear in my app, then don't reappear the next time I load 
my app.


Thanks.


-
To unsubscribe, send email to [EMAIL PROTECTED]
-