Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <878526.1194399590726.JavaMail.jira@brutus>
Date: Tue, 6 Nov 2007 17:39:50 -0800 (PST)
From: "Myrna van Lunteren (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Created: (DERBY-3182) fifth parameter (boolean isNullable)
 in DatabaseMetaData.getBestRowIdentifier(.....)  has no effect
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

fifth parameter (boolean isNullable) in DatabaseMetaData.getBestRowIdentifier(.....)  has no effect
---------------------------------------------------------------------------------------------------

                 Key: DERBY-3182
                 URL: https://issues.apache.org/jira/browse/DERBY-3182
             Project: Derby
          Issue Type: Bug
    Affects Versions: 10.3.1.4, 10.2.2.0, 10.2.1.6, 10.1.3.1, 10.1.2.1, 10.1.1.0, 10.0.2.1, 10.0.2.0
            Reporter: Myrna van Lunteren


The fifth parameter in a call to DatabaseMetaData.getBestRowIdentifier(String catalog, String schema, String table, int scope, boolean nullable) is getting ignored.

Thus, in the following situation:
        s.execute("create table a (i int not null, j int not null, k int, unique (i,j))");
        s.execute("insert into a values (1,1,1)");  
        DatabaseMetaData dmd = conn.getMetaData(); 

The call:
            ResultSet rs = dmd.getBestRowIdentifier(null,"APP","A",0,true);
gives the same results(columns i & j) as
            ResultSet rs = dmd.getBestRowIdentifier(null,"APP","A",0,false);

This has been documented as incorrect in the test bestrowidentifier.sql but I could not find any bug logged.
The text in bestrowidentifier was:
-- REMIND: we aren't handling nullOk flag correctly
-- we just drop nullable cols, we should skip an answer
-- that has nullable cols in it instead and look for another one.
create table t13 (i int not null, j int not null, k int, unique (i,j));

-- result: columns i, j (WRONG) 
-- the correct answer is k: the non-null columns of the table
execute bestrow using 'values(''APP'',''T13'',0,''false'')';

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