S
Screwtape
Guest
With Progress 9.1e, I'm using dynamic queries to make extensible data extracts.
I'm using a query of the form
FOR EACH tableName FIELDS( fieldName1 fieldName2 ) NO-LOCK
WHERE fieldName3 = "Value"
AND fieldName4 = "AnotherValue"
and for some of these queries, notably the ones with few fields in the table, the fields phrase is working and retrieving only the requested.
However, on other queries, interestingly the ones with much longer, and complicated field lists (including arrays etc.), it retrieves the whole record.
I've read various discussions on retrieving additional fields required for joins, but I've simplified my queries so that isn't an issue.
The query specifies no-lock, as does the get-next parameter, so the full-record for exclusive lock shouldn't be relevant either.
Are there other criteria by which Progress decides to select the entire record, and is there any way of stopping it?
Continue reading...
I'm using a query of the form
FOR EACH tableName FIELDS( fieldName1 fieldName2 ) NO-LOCK
WHERE fieldName3 = "Value"
AND fieldName4 = "AnotherValue"
and for some of these queries, notably the ones with few fields in the table, the fields phrase is working and retrieving only the requested.
However, on other queries, interestingly the ones with much longer, and complicated field lists (including arrays etc.), it retrieves the whole record.
I've read various discussions on retrieving additional fields required for joins, but I've simplified my queries so that isn't an issue.
The query specifies no-lock, as does the get-next parameter, so the full-record for exclusive lock shouldn't be relevant either.
Are there other criteria by which Progress decides to select the entire record, and is there any way of stopping it?
Continue reading...