Hi

I double-check changes to the db by running the SQLite3 client in a terminal. 
The memory db is only accessible by the same client/session so it won’t work. I 
also run multiple processes doing different things in the same image so each 
process needs its own connection/handle to SQLite3 so that wont work either.

I am using DROP TABLE IF NOT EXISTS to drop all tables before the main schema 
and it works perfectly.

But I did think of using a SQLite3 memory db to hold session info - i.e, 
cookies. Or I could just use a Dictionary. I haven’t implemented this yet but 
does anyone have any thoughts?

Vince

Reply via email to