once again, 2 months later.... I didn't even know of an extra_fields argument to SQLFORM. To be fair, though, I always though about virtual fields as something you need to show, not something you need to fill. By definition virtual Fields are something that closely follow the functionality of computed fields, but have the "feature" (I wouldn't dare to say "added benefit") to be calculated at each time, and not stored in the db. I don't know about the breaking of backwards compatibility argument.... virtual Fields in forms is something that I tend to consider out of scope, because usually a "virtual field" "functionality" in a SQLFORM is better suited for a SQLFORM.factory.
On Wednesday, September 24, 2014 7:19:33 PM UTC+2, Leonel Câmara wrote: > > I think the bug here is that Table.__iter__ doesn't return the same thing > as the first positions on the tuples coming from Table.items this is a very > odd and unexpected behavior. > -- 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.
