Pedro Vale de Gato wrote:
> Hi,
>
> In one of the apps i'm implementing i have found a limitation in the
> datanav framework when using virtualFields.
>
> If you define a filter for a virtualField on the select page it wont
> work, as it will try to filter the virtualField at SQL level, where it
> doesn't exist....
>
> I'd like to suggest a change to datanav that would make this possible:
>
> SelectPage.selectedFields would have another bool key "virtual", for
> example:
>
> self.selectFields["FIELDNAME"] = {
> "ctrl" : ctrl,
> "op" : opList,
> "type": "int",
> "virtual": True
> }
>
>
> Based on this information we would construct the query excluding virtual
> fields and requery()
>
> After that, if there were virtual fields, filter() the dataset based on
> the virtual fields only
Does filter()ing virtual fields work?
> I think it is the best way to do it, and am willing to do it, so please
> comment on my approach
If it works, and you are willing to do it...
> Is is already possible to do this? If so, how?
Well if the virtual field in question is completely derived from values in the
database already, I think that that should be what you select on, although your
way
is more database-agnostic...
Paul
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message: http://leafe.com/archives/byMID/[email protected]
