Now I understand: rows = db(...).select(...) rows.compact = False
and now you always have the rows[i].table.field syntax. no more rows[i].field shortcuts. Massimo On Aug 9, 1:06 pm, Marin Pranjic <marin.pran...@gmail.com> wrote: > No, but it would not help me. > > I want to implement "dynamic queries", actually support adding some > WHERE and SELECT parts in query (extending original queries). > And iteration through Rows object should work without knowing did > query had JOINs or not. > Problem is when original query does not have JOIN, and I extend them > with something which adds join. > Here syntax changes from row.fieldname to row.tablename.fieldname and > my view raises an exception. > > > > > > > > On Tue, Aug 9, 2011 at 12:33 AM, pbreit <pbreitenb...@gmail.com> wrote: > > I run into that problem a lot as well and haven't figured out the best way > > to handle it. > > Is it possible to do something like this? > > for item, auth_user in rows.item, rows.auth_user: > > ...
