1, Each FLWR expression has one or more for clause, one or more let clause, an optional where clause, and a return clause.

2, For the first time, you see that a for clause can define more than one variable.

3, The for clause binds the variable $y to each address in turn.

4, By using the for clause in the after-aggregation detail filter on a non-projected data item, the underlying query automatically projects and groups the item as the outer most column of the list.

5, The for clause binds variable $p to each of these ProductID values in turn.

6, The FOR clause of this function loops through the entity nodes contained in the transient XML data.

7, The distinct-values function in the for clause returns a list of all the distinct values of ProductID that are found inside comments in the Comments column of the Items table.

8, For now, though,[http:///for clause.html] always ensure you have the variable defined in your for clause reappearing in your return clause.

9, Finally, and most importantly, this will ignore any filtering or ordering you perform on the node set returned by the for clause.

10, The comprehension consists of a single expression followed by at least one for clause and zero or more for or if clauses.

11, Take a look at the example in Listing 2, which uses more than one for clause.

12, Without the FETCH FIRST (or similarly, but not exactly, without an OPTIMIZE FOR clause), then DB2 would almost certainly prefer some other access path.

13, According to the FLWR expression characteristics, the algorithm is divided into three parts: decomposing the LET and FOR clause, handling RETURN clause and WHERE condition.

14, Ensure that the user ID or PUBLIC is defined in the WITH USE FOR clause of the trusted context.

15, Listing 7 defines a sequence of names, and then uses a for clause to loop through this sequence, retrieving each name and adding it to a node collection.

16, In addition to the let and return clauses, Zorba supports for sequences, as well as the for clause to process them.