Page History
...
One of the primary jobs of a foundset is to load records from the table to which it is bound. A foundset is always based on an underlying SQL query, which may change often during the lifetime of the foundset. However the query will always take the form of selecting the Primary Key column(s) from the table and will also always include an ORDER BY
clause, which in its simplest form will sort the results based on the Primary Key column(s).
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
SELECT customerid FROM customers ORDER BY customerid ASC |
After retrieving the results for Primary Key data, the foundset will issue subsequent SQL queries to load the matching record data in smaller, optimized blocks. This query happens automatically in an on-demand fashion to satisfy the foundset's scrollable interface.
Code Block | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
SELECT * FROM customers WHERE customerid IN (?,?,?,?,?,?,?,?) ORDER BY customerid ASC |
...
The result is that all records are sorted by last name. But in the case where the last names are the same, then the first name is used.
|| last_name || first_name ||
Sloan | Zachary |
Smith | Jane |
Smith | Jon |
Snead | Aaron |
Available Data Provider Types
...
Gliffy Diagram | ||||
---|---|---|---|---|
|
Note |
---|
If relation is invalid relation name will return null in scripting. There is a helper method: databaseManager.hasRecords(JSRecord, relationName) to check if a related foundset is valid and has records. |
Foundsets and Data Broadcasting
...