You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, FBResultSetMetaData.getExtendedFieldInfo generates a big UNION for each individual combination of table + field to get the extended field info.
This might be optimizable in two ways:
Generate a query fragment per table for all fields of the table used in the query (or maybe even all fields of the table), instead of a fragment per table+field
Given extended field info is currently only used to determine precision of NUMERIC and DECIMAL columns, restrict the query to only return results for those types of columns (either by restriction in the query itself, or by filtering on column types when generating the query).
The text was updated successfully, but these errors were encountered:
Includes:
#731 FBResultSetMetaData.getExtendedFieldInfo will query same set of fields when there are more than 70 fields
#732 Optimize FBResultSetMetaData.getExtendedFieldInfo
#793 Report true for ResultSetMetaData.isAutoIncrement for identity columns
#795 Add connection property to disable retrieval of extended field info for ResultSetMetaData
#795 Implement disabling of retrieval of extended field info for ResultSetMetaData
Currently,
FBResultSetMetaData.getExtendedFieldInfo
generates a big UNION for each individual combination of table + field to get the extended field info.This might be optimizable in two ways:
The text was updated successfully, but these errors were encountered: