[web2py] Re: Remote admin of sqlite - through ssh

[wdtatenh]

Unfortunately, the update didn't occur (was not a schema change) - simple 
insert to auth_membership table.  Could see change when using local 
cmd/python shell.  Wasn't visible when I check using appadamin.  

sqlite is fine in this case because the site is not a high traffic site and 
very low concurrency for transactions which are not monetary.

[web2py] Re: Remote admin of sqlite - through ssh

[nick name]

On Sunday, June 10, 2012 6:18:26 AM UTC-4, wdtatenh wrote:

 Unfortunately, the update didn't occur (was not a schema change) - simple 
 insert to auth_membership table.  Could see change when using local 
 cmd/python shell.  Wasn't visible when I check using appadamin.  

 sqlite is fine in this case because the site is not a high traffic site 
 and very low concurrency for transactions which are not monetary.


Then you had some transaction issues going on - e.g. you forgot to commit 
or something like that. 

If you use the sqlite3 command line tool, it should default to auto-commit, 
but you can be sure by typing commit;

If you were doing it using dbapi, make sure you commit before closing the 
database.

[web2py] Re: Remote admin of sqlite - through ssh

[Anthony]

Were you doing the inserts via a web2py shell? If so, you need to call 
db.commit() for the changes to be committed (db.commit() is allowed but not 
necessary in regular web2py application code because each request is 
automatically wrapped in a db transaction and committed at the end of the 
request).

Anthony

On Sunday, June 10, 2012 6:18:26 AM UTC-4, wdtatenh wrote:

 Unfortunately, the update didn't occur (was not a schema change) - simple 
 insert to auth_membership table.  Could see change when using local 
 cmd/python shell.  Wasn't visible when I check using appadamin.  

 sqlite is fine in this case because the site is not a high traffic site 
 and very low concurrency for transactions which are not monetary.