On Tuesday, May 5, 2015 at 9:47:10 PM UTC+2, Massimiliano wrote: > > > I understand but get things screwed as you as saying is a programming > error. >
There are things that are not "foreseen" by developers and web2py generally doesn't do lots of typechecking (under the consensum that who approaches python is a "consenting adult"). Granted, if someone is using a shortcut for its restricted usecase scenario and then something breaks, he's not a happy man....but he was indeed using a shortcut that would break in the all-usercase-scenarios. Something documented as "*field_id must be the field of the table to be used as ID*" isn't really prone to interpretations :-P > It also always worked that way and no one complain about it. :-) > Nobody used it that way, and the fact that it works has nothing to do with web2py code, but a fortunate coincidence on your side > Was useful, flexible and cheaper. :-D > all of the above, with the little side-effect of being unmaintainable as soon as a new fix gets pushed in (such as the one you faced, required for a strict and correct ordering). same goes for the next enhancement, and for new features. -- 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.
