As explain Simone in case of passing id to javascript it requires refactoring of app... Also it brake silently a javascript plugin integrated manually as a field widget (not a custom widget). I gues I should have a made some test to cover that, but I am still exploring how the best way to manage test in web2py.
But, I don't understand (didn't read search the mailing-list) what was the motivation and the advantage of this change... Was it related to the bigint change talked about several month ago? It was suppose to be default to integer (what it was until now) and option in for bigint... Richard On Fri, Jun 21, 2013 at 7:43 AM, Alan Etkin <[email protected]> wrote: > I think it is not in the change log and it is not acceptable.... >> > > Hi Richard. Why it is not acceptable? Did the change break a documented > feature? How? > > Perhaps you want to post an issue in the project page ( > code.google.com/p/web2py/issues). If you do, please post as much > information you have collected about the problem as you can including > source code, error tracebacks, OS, db and web2py version, DAL adapter name > and the section of the book with the documented feature that is not working. > > > -- > > --- > 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/groups/opt_out. > > > -- --- 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/groups/opt_out.
