Sorry to jump in... Trying to get as much info as I can because I really need to get this to work (soon)... If I didn't have to actually install mySQL on everywhere I have this running, I'd would just use that (thing seems easier with mysql....
So, to understand, the DB's parent folder MUST be named 'databases'? and the DB MUST be called storage.db or storage.sqlite? if not, I will not be able to connect to existing DB? That's one thing I didn't make easy to change, but that is one thing I never tried either. So, I will. Also, I found this in a thread (from sometime last year) while looking for hints, would you know how it fits into what you mention above? Thanks, Mart :) from: http://groups.google.com/group/web2py/browse_thread/thread/8900d976810fbe20/67ced75de797e3d1?lnk=gst&q=connect+to+existing+db#67ced75de797e3d1 " 1) You should "initialize" (in the term of Ruby) a SQLTable object with "migrate" flag set to False (see db.define_table), thus WEB2PY will assume that you already has this table and will use it without trying to create it. 2) All WEB2PY needs in order to store the sessions data in a database: session.connect(request,response,db) This will create a table, following web2py_session_applicationname naming convention, with the following structure: `id` int(11) NOT NULL auto_increment, `locked` char(1) default NULL, `client_ip` varchar(64) default NULL, `created_datetime` datetime default NULL, `modified_datetime` datetime default NULL, `unique_key` varchar(64) default NULL, `session_data` longblob " On Feb 24, 8:51 pm, pbreit <[email protected]> wrote: > I suspect you may need to let Web2py create an "id" field since it usually > expects one (but I'm not totally sure). I would make sure you have a copy of > you're DB stored somewhere safe. And then maybe go ahead and let Web2py > migrate and see what happens. Tables normally have a primary key. > > I guess the only other thing is setting a connection > string:http://web2py.com/book/default/chapter/06#Connection-Strings > > Web2py expects an SQLite DB to be in the "databases" directory and named as > specified in the connection string (ie, "storage.db")(I think the "welcome" > app names it "storage.sqlite").
