Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 84939 invoked from network); 2 Nov 2010 09:22:42 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 2 Nov 2010 09:22:42 -0000 Received: (qmail 44535 invoked by uid 500); 2 Nov 2010 09:23:13 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 44319 invoked by uid 500); 2 Nov 2010 09:23:10 -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 44301 invoked by uid 99); 2 Nov 2010 09:23:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Nov 2010 09:23:09 +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.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Nov 2010 09:23:09 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oA29MmLI020381 for ; Tue, 2 Nov 2010 09:22:48 GMT Message-ID: <10828653.190401288689768635.JavaMail.jira@thor> Date: Tue, 2 Nov 2010 05:22:48 -0400 (EDT) From: "Knut Anders Hatlen (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-4772) Data truncation error with XPLAIN-functionality enabled In-Reply-To: <27771697.330121281705916094.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927337#action_12927337 ] Knut Anders Hatlen commented on DERBY-4772: ------------------------------------------- Hi Kristian, The patch looks like a good improvement (both increasing the length and changing the type to VARCHAR), but is there any particular reason why we should limit the strings to 128 and to the maximum length of a VARCHAR (32672)? > Data truncation error with XPLAIN-functionality enabled > ------------------------------------------------------- > > Key: DERBY-4772 > URL: https://issues.apache.org/jira/browse/DERBY-4772 > Project: Derby > Issue Type: Bug > Components: SQL > Affects Versions: 10.6.2.1, 10.7.1.0 > Reporter: Kristian Waagan > Assignee: Kristian Waagan > Attachments: derby-4772-1a-increase_max_len.diff > > > When running a modified version of lang.OrderByAndSortAvoidance I get the following error: > java.sql.SQLDataException: A truncation error was encountered trying to shrink CHAR 'Thread[DRDAConnThread_3,5,derby.daemons]' to length 32. > at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:79) > at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Util.java:256) > at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(TransactionResourceImpl.java:391) > at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(TransactionResourceImpl.java:346) > at org.apache.derby.impl.jdbc.EmbedConnection.handleException(EmbedConnection.java:2269) > at org.apache.derby.impl.jdbc.ConnectionChild.handleException(ConnectionChild.java:81) > at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(EmbedStatement.java:1321) > at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(EmbedPreparedStatement.java:1673) > at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeUpdate(EmbedPreparedStatement.java:303) > at org.apache.derby.impl.sql.execute.xplain.XPLAINSystemTableVisitor.addStmtDescriptorsToSystemCatalog(XPLAINSystemTableVisitor.java:390) > at org.apache.derby.impl.sql.execute.xplain.XPLAINSystemTableVisitor.doXPLAIN(XPLAINSystemTableVisitor.java:317) > at org.apache.derby.impl.sql.execute.NoPutResultSetImpl.close(NoPutResultSetImpl.java:179) > at org.apache.derby.impl.sql.execute.SortResultSet.close(SortResultSet.java:467) > at org.apache.derby.impl.jdbc.EmbedResultSet.close(EmbedResultSet.java:575) > at org.apache.derby.impl.drda.DRDAResultSet.close(DRDAResultSet.java:338) > at org.apache.derby.impl.drda.DRDAStatement.rsClose(DRDAStatement.java:995) > at org.apache.derby.impl.drda.DRDAConnThread.doneData(DRDAConnThread.java:7446) > at org.apache.derby.impl.drda.DRDAConnThread.writeFDODTA(DRDAConnThread.java:7026) > at org.apache.derby.impl.drda.DRDAConnThread.writeQRYDTA(DRDAConnThread.java:6910) > at org.apache.derby.impl.drda.DRDAConnThread.processCommands(DRDAConnThread.java:870) > at org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java:294) > Caused by: java.sql.SQLException: A truncation error was encountered trying to shrink CHAR 'Thread[DRDAConnThread_3,5,derby.daemons]' to length 32. > 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) > ... 20 more > Caused by: ERROR 22001: A truncation error was encountered trying to shrink CHAR 'Thread[DRDAConnThread_3,5,derby.daemons]' to length 32. > at org.apache.derby.iapi.error.StandardException.newException(StandardException.java:343) > at org.apache.derby.iapi.types.SQLChar.hasNonBlankChars(SQLChar.java:1767) > at org.apache.derby.iapi.types.SQLChar.normalize(SQLChar.java:1743) > at org.apache.derby.iapi.types.SQLChar.normalize(SQLChar.java:1695) > at org.apache.derby.iapi.types.DataTypeDescriptor.normalize(DataTypeDescriptor.java:648) > at org.apache.derby.impl.sql.execute.NormalizeResultSet.normalizeColumn(NormalizeResultSet.java:329) > at org.apache.derby.impl.sql.execute.NormalizeResultSet.normalizeRow(NormalizeResultSet.java:373) > at org.apache.derby.impl.sql.execute.NormalizeResultSet.getNextRowCore(NormalizeResultSet.java:188) > at org.apache.derby.impl.sql.execute.DMLWriteResultSet.getNextRowCore(DMLWriteResultSet.java:127) > at org.apache.derby.impl.sql.execute.InsertResultSet.open(InsertResultSet.java:504) > at org.apache.derby.impl.sql.GenericPreparedStatement.executeStmt(GenericPreparedStatement.java:436) > at org.apache.derby.impl.sql.GenericPreparedStatement.execute(GenericPreparedStatement.java:317) > at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(EmbedStatement.java:1232) > ... 14 more > I suspect the error can be triggered easily in client/server, but for convenience I'll attach the patch for the test where I see the issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.