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
If a result set has more than 70 columns, the implementation of getExtendedFieldInfo in FBResultSetMetaData will break this up into querying per 70 fields. However, the code has a bug where it will start over with column 1, so it will query the columns it already queried, instead of querying the next 70 columns.
Since this bug seems to have existed since Jaybird 1, and there is graceful degradation, this will only be fixed in Jaybird 6.
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
If a result set has more than 70 columns, the implementation of
getExtendedFieldInfo
inFBResultSetMetaData
will break this up into querying per 70 fields. However, the code has a bug where it will start over with column 1, so it will query the columns it already queried, instead of querying the next 70 columns.Since this bug seems to have existed since Jaybird 1, and there is graceful degradation, this will only be fixed in Jaybird 6.
The text was updated successfully, but these errors were encountered: