I was about to do this when I encountered a logical problem...
db.define_table('table1',SQLField('name',label='Name'))
db.define_table('table2',SQLField('name',label='Name'),SQLField
('other_id',db.table1))
{{=db(db.table1.id==db.table2.other_id).select()}}
this makes a JOIN so the table headers involve two tables.
currently the header is
table1.name, table2.name
if I use label, the header would be:
Name, Name
because a label makes sense only within the context of a table, not
two joint tables.
the current mechanism is to do
{{=db(db.table1.id==db.table2.other_id).select()}}
{{=SQLTABLE(db(db.table1.id==db.table2.other_id).select(),headers=
{'table1.name':'Fisrt table Name', 'table2.name':'Second Table
Name'})}}
which makes
First Table Name, Second Table Name
is this sufficient? Pros Cons Suggestions?
Massimo
On Jan 15, 8:02 am, mdipierro <mdipie...@cs.depaul.edu> wrote:
> I agree. In 1.56.
>
> On Jan 15, 5:10 am, vince <lapcc...@gmail.com> wrote:
>
> > i think SQLTABLE header should read the predefined label as well as
> > SQLFORM
>
> > -vince
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py Web Framework" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to
web2py+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
