Hi, correct, no records 24031-24040. I was thinking that my variables maybe would have contained something not acceptable so I changed all variables, but still can't insert.
Feels like an roolback, but why earth it would do something like that I don't understand. There definitly aren't any roolbacks in the code as I didn't know there was anything like that. Kenneth Den onsdag 25 april 2018 kl. 17:54:07 UTC+3 skrev Anthony: > > On Tuesday, April 24, 2018 at 4:20:18 PM UTC-4, Kenneth wrote: >> >> The function that contains this does a lot of things, but nothing else >> regarding this table. And no values are not hard coded, just trying to find >> out the problem so I made it as simple as possible. >> >> If I look at the table in MySQL prompt is see that highest record ID is >> lets say 24030, I run the controller 10 times and look at the table again, >> still highest record is 24030. If I at this moment insert a record manually >> from MySQL prompt it'll get ID, 24041. >> > > But when you query MySQL (from the prompt or from web2py) there are no > records whose IDs are 24031 through 24040? > > If so, is it possible the inserts made from web2py are being rolled back > (either because an exception is being raised or via an explicit > db.rollback)? In that case, I believe MySQL will increment the IDs even > though the transaction is ultimately rolled back. > > Anthony > -- 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.
