> You only use ajax if the option of field2 depend o selection for
> field1 and you always end up with usability problems when field1 and 2
> are in the same form (because of the ajax delay).
>
> If the options depend on the logged in user it can be done without
> ajax. How depends on details.
>
You only use ajax if the option of field2 depend o selection for
field1 and you always end up with usability problems when field1 and 2
are in the same form (because of the ajax delay).
If the options depend on the logged in user it can be done without
ajax. How depends on details.
On 9 Lug, 09:
I have a related query.
> On Jul 9, 12:35 am, David Marko wrote:
>> You can use full DAL query in IS_IN_DB validator e.g.
>> IS_IN_DB(db(db.children.sex=='M'),'children.id','%(name)s' )
I want the result of IS_IN_DB to be part of my access control measures
and dependent on who is logged in and w
I thought there was an easier way. I didn't think of just passing it
in with db in the first place. Thanks
On Jul 9, 12:35 am, David Marko wrote:
> You can use full DAL query in IS_IN_DB validator e.g.
> IS_IN_DB(db(db.children.sex=='M'),'children.id','%(name)s' )
>
> David
>
> On 9 čnc, 08:08, A
You can use full DAL query in IS_IN_DB validator e.g.
IS_IN_DB(db(db.children.sex=='M'),'children.id','%(name)s' )
David
On 9 čnc, 08:08, Alastair Medford wrote:
> As it stands, when one places the IS_IN_DB validator on a field, you
> get a select list with options of all the rows in the given t
5 matches
Mail list logo
