> My team and I are used to working with object-oriented ORM, and that's why > the "self" feels more natural to me (and my lazy side says that there are > many innecesary characters...), I mean that why not pass only the row > object, "row" is an object of type row, and row.table is a row object too, > I don't understand why is passed "row" if we always are going to work with > "row.table" >
As mentioned, the old style virtual fields could be applied to joins, in which case, you must always access individual field values via row.tablename.fieldname notation. Perhaps the new style virtual fields adopted this same approach to be consistent. I agree, though, it would be nicer to allow row.fieldname notation -- maybe submit a feature request. Anthony -- 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.
