Hi Anthony,
it is working now, sorry for the inconvenience.
Thanks again!
On Friday, September 27, 2013 4:40:05 PM UTC+2, Anthony wrote:
>
> Can you show your exact code (the code you showed can't be the code you're
> using, as there would be no add or edit buttons with that code)? It
> definite
Can you show your exact code (the code you showed can't be the code you're
using, as there would be no add or edit buttons with that code)? It
definitely works when I try it.
Anthony
On Friday, September 27, 2013 9:22:37 AM UTC-4, Mirko wrote:
>
> Hi Anthony, and thanks for answering.
>
> Actua
Hi Anthony, and thanks for answering.
Actually
db.person._format = lambda row: '%s' % row.name.upper()
doesnt not affect the dropdown list building...
I had to add this
db.thing.owner_id.requires=IS_IN_DB(db,'person.id',lambda row: '%s' %
row.name.upper())
to have the dropdown list in upper
The dropdown on a create/edit form is not controlled by the field's
represent attribute -- instead, it is the field's IS_IN_DB validator that
creates the dropdown. So, you could either manually override the default
IS_IN_DB validator, or just change the db.person._format attribute, which
will a
Here's a code example :
db definition:
db.define_table('person', Field('name'), format='%(name)s')
db.define_table('thing', Field('name'), Field('owner_id','reference
person'), format='%(name)s')
controller:
def manage_test():
db.thing.owner_id.represent=lambda id, row: '%s' %
db.person[ro
5 matches
Mail list logo
