Assertion: cursor's data | /r/HasProperty | fetched
Facets:
value: from the database
type: LOCATION
value: depending on the data
type: OTHER
Source sentences:
text: When the data is fetched it is copied to the record or variables and the logical pointer moves to the next row and it becomes the current row.
text: Data is fetched from the database depending on the data specified in the SELECT statement along with its additions.
text: record_list> represents the list of variables that will receive the data being fetched.
text: As you can see from the output, the SQL Projection describing what columns were going to be returned by the query, and what their datatypes are etc. has been determined before any data has been fetched.
text: The cursor processing needs to know what columns are going to be produced before the data is fetched, so the columns cannot be based on what data may or may not be there.
text: The projection of an SQL statement must be known by the SQL engine before any data is fetched, so don't expect SQL to magically create columns on-the-fly based on the data it's retrieving back; and, if you find yourself thinking of using dynamic SQL to get around it, just take a step back and see if what you are trying to achieve may be better done elsewhere, such as in a reporting tool or the user interface.