Hmm... That's gonna be a problem. This is occurring in an SQLFORM... which is in a modal pop-up box... over a tabbed structure with about 5 more SQLFORMS... plus 5 or 6 jQuery DataTables... all powered by the same basic set of 4 or 5 tables. It will take a solid day to boil it down to a simpler example which could be posted successfully.
I'm hoping to get a sense of the philosophy of the new code, so I can debug it myself and figure out if it could be fixed for this case. It seems that each Field is "bound" to a Table when a query is performed. I presume this binding has always occurred, yet now it is causing this obscure error. I'm not sure why it would ever be an error to bind the same field to the same table, and it seems that this "case" should be the most frequently encountered. Now I'll admit it DOES bother me A LOT to place a database instance INSIDE the Field and the Table objects. I'd think that would be a very poor idea if you wanted your design to be a clean and free from hidden side effects. My biggest fear is that DAL has taken a direction which will make it incompatible with my use, and that I'll never be able to use 2.15.1 or later versions. I'm weeks away from deploying the biggest site I've ever done. As of this second, my best short-term option is to revert to the previous version of web2py and finish. But that has severe long-term repercussions if I can't update my web platform in the future. -- Joe On Saturday, July 15, 2017 at 3:53:40 AM UTC-7, Anthony wrote: > > As usual, I think we need to see some code and a traceback. -- 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.
