Changes between Version 24 and Version 25 of S3/S3ResourceFilter

Timestamp:

06/13/14 12:17:48 (10 years ago)

Author:

MattS

Comment:

syntax highlighting

S3/S3ResourceFilter

@@ -121 +121 @@
 S3FieldSelector instances can also be generated at the back-end, simply by:
 
-{{{
+{{{#!python
 selector = S3FieldSelector(<field selector>)
 }}}
@@ -127 +127 @@
 Such selectors can then be used to create filter queries, using a syntax very similar to web2py queries:
 
-{{{
+{{{#!python
 afilter = S3FieldSelector("person.first_name") == "Dominic"
 bfilter = ~(S3FieldSelector("person.first_name").like("Dominic"))  # negation by ~ operator
@@ -149 +149 @@
 These filter queries can also be joined together by {{{&}}} and {{{|}}} operators:
 
-{{{
+{{{#!python
 cfilter = (S3FieldSelector("person.first_name") == "Dominic") & (S3FieldSelector("contact.value") == "dominic@nursix.org")
 }}}
@@ -157 +157 @@
 To add a filter to a resource is as simple as:
 
-{{{
+{{{#!python
 myfilter = S3FieldSelector("person.first_name") == "Dominic"
 resource.add_filter(myfilter)
@@ -166 +166 @@
 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.
 
-{{{
+{{{#!python
 myfilter = db.pr_contact.value == "dominic@nursix.org"
 resource.add_filter(myfilter, c="contact")