I just switched to Version 2.15.1-stable+timestamp.2017.07.10.16.17.24 and I'm getting a new and very unwelcome error.
ValueError: Field <blah> is already bound to a table Yeah. I knew that. In fact, the field is already bound to exactly the SAME table in other queries. So what? Why is that now an error? I double-checked and sure enough the table its bound to is exactly the table that it would be bound to if the "bind" function completes. (Although the table._db of the already bound table has a "real" URI and the not-yet-bound table has a table._db lacking a real URI.) Why have I never seen this error before? I've been developing this app on and off for a couple of years and this is the first time I've seen this problem. Is it by chance new with 2.15.1? What is the purpose of this error? What binding is occurring? (I'm guessing this is the binding in the driver immediately before a query.) Why can this binding only happen once? Is it happening because I do the heavy lifting in modules instead of controllers? I often use the same tables more than once in a function, so this could be problematic (read: fatal) in my adoption of 2.15.1. -- Joe -- 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.
