Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Thu, 13 Oct 2011 03:23:11 +0000 (UTC)
From: "Dag H. Wanvik (Created) (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <604900336.7749.1318476191940.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (DERBY-5459) Result set metadata are out of sync
 on client after underlying table is altered
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Result set metadata are out of sync on client after underlying table is altered
-------------------------------------------------------------------------------

                 Key: DERBY-5459
                 URL: https://issues.apache.org/jira/browse/DERBY-5459
             Project: Derby
          Issue Type: Bug
            Reporter: Dag H. Wanvik


Cf the discussion on DERBY-3823.

The enclosed repro program shows what happens. When I run it with
client/server and embedded respectively we see these two differing
results:

client/server:

$ java -cp .:$CLASSPATH Repo
Done loading data
executing alter
execp.getResultDescription: select * from t1
2. PS#getMetaData: char column length is 8
Reexecuting ps on changed table...
3. RS#getMetadata: char column length is 8
data:1 12345678

dag@T61pOS:~/java/sb/apps/derby3823$ !rm
rm -rf DERBY3823DB

embedded:

dag@T61pOS:~/java/sb/apps/derby3823$ java -cp .:$CLASSPATH Repro 2
execp.getResultDescription: insert into t1 values(?,'aaaaa')
execp.getResultDescription: insert into t1 values(?,'aaaaa')
Done loading data
execp.getResultDescription: select * from t1
execp.getResultDescription: select * from t1
executing alter
2. PS#getMetaData: char column length is 5
Reexecuting ps on changed tableh...
3. RS#getMetadata: char column length is 5
data:1 12345678


As we can see, the metadata results are different after the ALTER
TABLE. The trace from EmbedPreparedData
("execp.getResultDescription:") lines (see repro-patch.diff) show that
after ALTER, the metadata are not refreshed on the server side.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira