Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Date: Fri, 03 Jul 2009 00:34:59 +0200
From: Dag.Wanvik@Sun.COM (Dag H. Wanvik)
Subject: Re: [jira] Updated: (DERBY-4160) getMetaData().getIndexInfo crashes
 with "ERROR X0Y68: Column 'PARAM1' already exists."
In-reply-to: <739425620.1246558307188.JavaMail.jira@brutus>
Sender: Dag.Wanvik@Sun.COM
To: derby-dev@db.apache.org
Message-id: <x1oxprcivhm4.fsf@sun.com>
References: <739425620.1246558307188.JavaMail.jira@brutus>
User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/22.1 (usg-unix-v)

"Rick Hillegas (JIRA)" <jira@apache.org> writes:

>      [ https://issues.apache.org/jira/browse/DERBY-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Rick Hillegas updated DERBY-4160:
> ---------------------------------
>
>       Issue & fix info:   (was: [Release Note Needed])
>                Urgency: Normal
>     Bug behavior facts:   (was: [Crash])
>
> Triaged July 2, 2009: This does not seem to satify our definition of a crash. I don't see why a release note is needed.

The auto-translation from "[Existing Application Impact" to [Release
Note Needed] was done here and shows that the original use of
"[Existing Application Impact]" was wrong (the poster had used it to
mean the bug had an impact on his application, rather than that the
*fix* would have an impact, most likely...).

Cf.

Dag H. Wanvik made changes - 30/Jun/09 09:12 AM
Field 	Original Value 	New Value
Issue & fix info 	[Existing Application Impact] 	[Release Note Needed] 

Dag


>
>> getMetaData().getIndexInfo crashes with "ERROR X0Y68: Column 'PARAM1' already exists."
>> --------------------------------------------------------------------------------------
>>
>>                 Key: DERBY-4160
>>                 URL: https://issues.apache.org/jira/browse/DERBY-4160
>>             Project: Derby
>>          Issue Type: Bug
>>          Components: SQL
>>    Affects Versions: 10.4.2.0
>>         Environment: FreeBSD java 1.6.0, 64-Bit Server VM; DataNucleus JDO
>>            Reporter: ArtemGr
>>
>> The following code in DataNucleus:
>> rs = conn.getMetaData().getIndexInfo(catalogName, schemaName, tableName, false,
>> true);
>> triggers an Exception (http://gist.github.com/95679):
>> Caused by: java.sql.SQLException: Column 'PARAM1' already exists.
>>         at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(SQLExceptionFactory.java:45)
>>         at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(SQLExceptionFactory40.java:119)
>>         at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:70)
>>         ... 105 more
>> Caused by: ERROR X0Y68: Column 'PARAM1' already exists.
>>         at org.apache.derby.iapi.error.StandardException.newException(StandardException.java:303)
>>         at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.duplicateDescriptorException(DataDictionaryImpl.java:1678)
>>         at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.addDescriptor(DataDictionaryImpl.java:1662)
>>         at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.addSPSParams(DataDictionaryImpl.java:3682)
>>         at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.updateSPS(DataDictionaryImpl.java:3830)
>>         at org.apache.derby.iapi.sql.dictionary.SPSDescriptor.updateSYSSTATEMENTS(SPSDescriptor.java:1112)
>>         at org.apache.derby.iapi.sql.dictionary.SPSDescriptor.getPreparedStatement(SPSDescriptor.java:736)
>>         at org.apache.derby.iapi.sql.dictionary.SPSDescriptor.getPreparedStatement(SPSDescriptor.java:642)
>>         at org.apache.derby.impl.sql.compile.ExecSPSNode.generate(ExecSPSNode.java:177)
>>         at org.apache.derby.impl.sql.GenericStatement.prepMinion(GenericStatement.java:447)
>>         at org.apache.derby.impl.sql.GenericStatement.prepare(GenericStatement.java:88)
>>         at org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.prepareInternalStatement(GenericLanguageConnectionContext.java:794)
>>         at org.apache.derby.impl.jdbc.EmbedPreparedStatement.<init>(EmbedPreparedStatement.java:128)
>>         ... 99 more
>
> -- 
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>

-- 
Dag H. Wanvik, staff engineer
Sun Microsystems, Databases (Java DB/Derby)
Haakon VII gt. 7b, N-7485 Trondheim, Norway
Tel: x43496/+47 73842196, Fax:  +47 73842101