Well, nothing unusual with my table definitions. Everything by the specs. I just removed all .table files and started with new sqlite file, and that problem is gone. (i still have copies)
Seems that files were stuck in some state. However, main.message error still confuses me, because sql query that's created by DAL is valid. And this happens even after migrations are fixed. So it's probably SQLite that's broken/corrupted and I'm not sure if those issues are somehow related. Marin On Sun, May 4, 2014 at 8:58 PM, Niphlod <niph...@gmail.com> wrote: > how are your table defined ? the fact that 'main.message' gets into the > error seems a little weird for a table named "message_receiver". Also, that > "success" repeated into sql.log means that something really strange is > going on with your migrations. > > > On Sunday, May 4, 2014 3:22:19 PM UTC+2, Marin Pranjić wrote: > >> To confirm... >> https://github.com/web2py/web2py/blob/master/gluon/dal.py#L1262 >> >> This gets executed on every request. >> >> However I still don't understand why sqlite fails on insert. >> >> It fails on testing server but it works on my local instance. >> >> Marin >> >> >> On Sun, May 4, 2014 at 3:13 PM, Marin Pranjić <marin....@gmail.com>wrote: >> >>> Hi. >>> >>> I have application hosted on EC2. It is a testing server. It's like >>> production environment except it uses SQLite. >>> >>> I have a table called message_receiver. When I fetch records (for ex. in >>> appadmin) it works, but when I try to insert something (appadmin or in-app) >>> i get the following error: >>> >>> OperationalError: no such table: main.message >>> >>> >>> >>> I got the actual SQL query from the error ticket: >>> >>> >>> >>> INSERT INTO message_receiver(time_seen,user_id,message_id) VALUES >>> (NULL,93,1); >>> >>> >>> >>> That seems correct. >>> >>> However, I noticed that my sql.log is bigger than sqlite database file. It >>> has lots of "success!" messages inside. >>> And it seems that migration for some tables is triggered on every request >>> but nothing changes in .table files. >>> >>> >>> >>> There are 6 tables that are affected by migration but I don't see a pattern. >>> >>> Can someone suggest how to trace/debug this? >>> >>> -- >>> 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 web2py+un...@googlegroups.com. >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > 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 web2py+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
