I understand but get things screwed as you as saying is a programming error.
It also always worked that way and no one complain about it. :-) Was useful, flexible and cheaper. :-D On Tue, May 5, 2015 at 8:48 PM, Niphlod <niph...@gmail.com> wrote: > as you're explaining it, you were using it wrongly. > field_id needs to be a field that comes from either the table you're > passing OR a field from a table that gets included when you pass a set, or > everything gets screwed: details, selectable, view, edit, etc use the > field_id to identify the record : it can't come from another table, even if > your view is calling it under the hood (but web2py doesn't know it) > > -- > 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. > -- Massimiliano -- 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.
