...
Name | Type | Cardinality |
---|---|---|
parameter | 0..n | |
cache | 0..1 | |
from | urn:com.cohga.server.data.database#1.0:from | 0..n |
where | urn:com.cohga.server.data.database#1.0:where | 0..n |
sort | urn:com.cohga.server.data.database#1.0:sort | 0..n |
join | urn:com.cohga.server.data.database#1.0:join | 0..n |
options | urn:com.cohga.server.data.database#1.0:options | 0..1 |
...
Sub-tags
Name | Type | Cardinality |
---|---|---|
from | 0..n | |
where | 0..n |
Content
None
Notes
- If no
label
is specified then it will be generated by formatting thename
, unless noname
is supplied, then it will be generated by formatting thecolumn
- Formatting involves converting any _'s to spaces, converting the first letter and any letter after a space to upper case and converting every other letter to lower case, e.g. "BOMB_DISPOSAL_METHOD" becomes "Bomb Disposal Method"
- Only one of
text
ortextcolumn
should be specified when type is 'url'
...
This example will utilise a temporary table called ROADS_SELECTION
which contains two columns RD_NAME
who's data type matches the RD_NAME
column in the ROADS
table, and UID
which is a varchar column long enough to contain 32 random characters, and there should be an non-unique index on the UID
column.
Note: that "userid" and "key" are the default names for the columns in the temporary table, they can be called anything but if they're not "userid" and/or "key" then you'd need to set the keycolumn
and usercolumn
values in the data defintiion to match the names of the columns in the temporary table, as has been done above since the column names are actually "RD_NAME" and "UID" rather than "userid" and "key". You always need to provide the keytable
parameter so there's no default for that.
Sorting data
You can add <sort> tags to specify what column(s) to sort by by default, e.g.
...