- The details of these commands are not important here; the important
+ The details of these commands are unimportant here; the important
point is that there are several separate updates involved to accomplish
this rather simple operation. Our bank's officers will want to be
assured that either all these updates happen, or none of them happen.
We already saw that ORDER BY> can be omitted if the ordering
- of rows is not important. It is also possible to omit PARTITION
+ of rows is unimportant. It is also possible to omit PARTITION
BY>, in which case there is just one partition containing all the rows.
This will match paths that contain the label Europe and
any label beginning with Russia (case-insensitive),
but not paths containing the label Transportation.
- The location of these words within the path is not important.
+ The location of these words within the path is unimportant.
Also, when %> is used, the word can be matched to any
underscore-separated word within a label, regardless of position.
b inputs will be concatenated, and forced to either
upper or lower case depending on the uppercase
parameter. The remaining details of this function
- definition are not important here (see for
+ definition are unimportant here (see for
more information).
In practice the
source_sql query should always
specify ORDER BY 1> to ensure that values with the same
row_name are brought together. However,
- ordering of the categories within a group is not important.
+ ordering of the categories within a group is unimportant.
Also, it is essential to be sure that the order of the
category_sql query's output matches the specified
output column order.