Changes between Version 12 and Version 13 of S3/S3ResourceFilter

Timestamp:

01/31/12 14:25:36 (13 years ago)

Author:

Dominic König

Comment:

--

S3/S3ResourceFilter

@@ -150 +150 @@
 }}}
 
-If your filter involves a component table, you may need to add the respective joins. This can be done simply by specifying the component alias in the add_filter call:
+Joins which become necessary for filters will be added automatically as long as you use S3ResourceQuery instances with add_filter.
+
+You can though also specify a standard web2py Query for add_filter, in which case you would have to specify the respective join manually. If you specify a component alias as "c" parameter, the join for this component would be added automatically.
 
 {{{
-myfilter = S3QueryField("contact.value") == "dominic@nursix.org"
-resource.add_filter(myfilter, c="contact")  # also adds the join for the "contact" component to the resource query
+myfilter = db.pr_contact.value == "dominic@nursix.org"
+resource.add_filter(myfilter, c="contact")
 }}}
 
-For URL filters, this happens automatically.
+Note that S3ResourceQuery instances are resource-agnostic, so they can be re-used across resources (provided the same field selector applies in all of them).
 
-Note that filters as such (i.e. S3ResourceQuery instances) are resource-agnostic, so they can be re-used across resources (provided the same field selector applies in all of them).
-
-Filters for fields which are not defined in a resource will be ignored quietly when retrieving records from the resource.
+S3ResourceQueries for fields which are not defined in a resource will be ignored quietly when retrieving records from the resource.