db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2797) Nullability of columns in result set for ODBC's SQLForeignKey function does not match ODBC API.
Date Mon, 06 Jul 2009 18:35:14 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rick Hillegas updated DERBY-2797:
---------------------------------

    Urgency: Normal

Triaged for 10.5.2: assigned normal urgency.

> Nullability of columns in result set for ODBC's SQLForeignKey function does not match
ODBC API.
> -----------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2797
>                 URL: https://issues.apache.org/jira/browse/DERBY-2797
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Miscellaneous
>    Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0,
10.3.1.4
>         Environment: Derby server with ODBC client.
>            Reporter: A B
>            Priority: Minor
>
> ODBC clearly states what the nullability for the various columns in a SQLFOREIGNKEYS
result set should be:
>   http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcsqlforeignkeys.asp
> But if such a call is made against the Derby server, columns 2, 6, 9, 12, and 13 all
have the wrong nullability.  This may be similar to the problems discussed in DERBY-2307,
but I haven't looked closely enough to say for sure.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message