Changes between Version 10 and Version 11 of S3/S3ResourceFilter

Timestamp:

01/31/12 14:10:00 (14 years ago)

Author:

Dominic König

Comment:

--

S3/S3ResourceFilter

@@ -150 +150 @@
 }}}
 
-Note that filters (S3ResourceQuery instances) are resource-agnostic, so they can be re-used across resources (provided the same field selector applies in all of them).
+If your filter involves a component table, you may need to add the respective joins. This can be done automatically, by specifying the component alias in the add_filter call:
+
+{{{
+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
+}}}
+
+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.