Hi weheh , 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 Mar 29, 6:52 am, weheh <richard_gor...@verizon.net> wrote: > Sorry for being long-winded above. The questions, simply stated: > > 1) How does one get web2py to point to and run directly off an > existing db made and updated by a Ruby app? > 2) How does one get a web2py app to share authentication and session > information with a Ruby app? > > I imagine no magic is needed to do this, but I'd like to hear from the > more experienced users how they would approach this. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
