Hi Gavin, Yes, you need to define tables again, but only in your "homemade task queues". In db.py you define tables only once. In your external app you have to define every time you use it. Mayby i'm wrong, because i'm new in web2py, but that works for my app. I think that's not define in database way (like CREATE table etc.), but you create some struct for DAL. You can't also define db global (http://web2py.com/books/default/chapter/29/04/the-core#Sharing-the-global-scope-with-modules-using-the-current-object) If i'm wrong can someone correct me ?
Regards Adam W dniu wtorek, 10 maja 2016 17:52:36 UTC+2 użytkownik Gavin Kenny napisał: > > Hi Adam, > > I am suprised you need to define the tables again. I would expect you > would open access to the database via a call to the DAL and then use an > insert command to add more information, or is that what you meant? > > regards > > Gavin > > On Tuesday, 10 May 2016 09:54:53 UTC+1, Adam Drzewiecki wrote: >> >> Hi. >> >> I'm writing a similar application - i'm logging clients events in >> database. >> I used homemade task queues to run listener. I start whole project with >> bat: >> >> start C:\Python27\python.exe web2py.py -S Test -M -R applications/Test/ >> private/server.py >> start C:\Python27\python.exe web2py.py >> >> Point of using DAL and homemade task queues is: >> >> Create once in db.py: >> db = DAL(...) >> db.define_table(...) >> >> and in your listener every time you want to use it: >> db = DAL(...) >> db.define_table(...) >> db.commit() >> >> Is that what you meant? >> Adam >> >> W dniu niedziela, 8 maja 2016 15:48:23 UTC+2 użytkownik Gavin Kenny >> napisał: >>> >>> Hi, >>> >>> I have been watching web2py for some time and really like it. I have >>> worked through a few basic examples but this is my first "real" project. I >>> am looking at making a simple Log manager, where I have a python listener >>> that parses incoming logs and then loads them into the database and then >>> use web2py as the front end. I would like to use the DAL as it then makes >>> migration between databases much easier if I need more performance etc. >>> >>> From reading this list and the book it would appear that I should spawn >>> the listener using the scheduler as this exposes the db instance etc but I >>> am really feeling my way and unsure if the scheduler is more for kicking >>> off specific tasks that run and then stop or if something that will sit and >>> run for ever is OK. >>> >>> Any pointers on how to achieve this would be gratefully received. >>> >>> regards >>> >>> Gavin >>> >> -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
