[
https://issues.apache.org/jira/browse/DERBY-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-3171:
----------------------------------
Issue & fix info: [Newcomer, Repro attached]
Urgency: Normal
Bug behavior facts: [Embedded/Client difference]
Triaged for 10.5.2. Set normal urgency
> ResultsetMetadata.isNullable returns different value for networkserver/client
> vs. embedded on some columns after a call to DatabaseMetaData.getAttributes()
> -----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3171
> URL: https://issues.apache.org/jira/browse/DERBY-3171
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.4.1.3
> Reporter: Myrna van Lunteren
> Priority: Trivial
>
> Code like the following:
> DatabaseMetaData dmd = <a connection>.getMetaData();
> ResultSet rs = dmd.getAttributes(null,null,null,null);
> ResultSetMetaData rsmd = rs.getMetaData();
> int actualCols = rsmd.getColumnCount();
> for (int i = 0; i < actualCols; i++)
> {
> System.out.println(rsmd.getColumnName(i+1));
> System.out.println(rsmd.isNullable(i+1));
> }
> Will return different values for a number of columns in the resultset for
> network server/client vs. embedded.
> See test fixture DatabaseMetaData.testUnimplementedSQLObjectAttributes().
> The difference shows up for: DATA_TYPE, ATTR_SIZE, DECIMAL_DIGITS,
> NUM_PREC_RADIX, NULLABLE, SQL_DATA_TYPE, SQL_DATETIME_SUB, CHAR_OCTET_LENGTH,
> ORDINAL_POSITION.
> It's unlikely that this would ever cause a problem for a user's application,
> so marking as trivial.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
