From derby-dev-return-72700-apmail-db-derby-dev-archive=db.apache.org@db.apache.org Wed Sep 02 14:16:57 2009 Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 76276 invoked from network); 2 Sep 2009 14:16:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 2 Sep 2009 14:16:57 -0000 Received: (qmail 12328 invoked by uid 500); 2 Sep 2009 14:16:56 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 12266 invoked by uid 500); 2 Sep 2009 14:16:56 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 12258 invoked by uid 99); 2 Sep 2009 14:16:56 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Sep 2009 14:16:56 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Sep 2009 14:16:53 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id B4703234C004 for ; Wed, 2 Sep 2009 07:16:32 -0700 (PDT) Message-ID: <1882958802.1251900992723.JavaMail.jira@brutus> Date: Wed, 2 Sep 2009 07:16:32 -0700 (PDT) From: "Bryan Pendleton (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-4284) All Columns become Nullable when Using left join In-Reply-To: <318850444.1245657007355.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-4284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750448#action_12750448 ] Bryan Pendleton commented on DERBY-4284: ---------------------------------------- That wisconsin.out change is intriguing. I vaguely remember a situation several years back when we updated the query plan in the ref file due to an ordered null semantics diff, and we couldn't figure out what had caused it, or why. Unfortunately I can't remember more of the details, but I'm hopeful that with this latest change we now have a tighter grip on the nullability of result columns. Thanks for investigating these issues in such detail! > All Columns become Nullable when Using left join > ------------------------------------------------ > > Key: DERBY-4284 > URL: https://issues.apache.org/jira/browse/DERBY-4284 > Project: Derby > Issue Type: Bug > Components: JDBC, SQL > Affects Versions: 10.5.1.1 > Environment: Microsoft Windows XP SP3, Sun JDK 6 Update 14 > Reporter: Chua Chee Seng > Assignee: Knut Anders Hatlen > Attachments: derby-4284-1a.diff, derby-4284-1b.diff, derby-4284-1b.stat, derby-4284-1c.diff, derby-4284-1c.stat, Main.java > > > Consider following:- > create table person ( > id varchar(20) not null, > name varchar(100) not null > ); > create table car ( > id varchar(20) not null, > person_id varchar(20) not null, > model varchar(100) not null, > plat_no varchar(100) not null > ); > When select :- > select > p.name, > c.model, > c.plat_no > from person p > left join car c on (p.id = c.person_id); > From the ResultSet, get the ResultSetMetaData and inspect each column's isNullable() value, which is always = 1 (always nullable). Expected : column 'p.name' isNullable = 0 (not nullable), but I get 'p.name' isNullable = 1 (nullable) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.