Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 12237 invoked from network); 25 Mar 2009 08:59:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 25 Mar 2009 08:59:13 -0000 Received: (qmail 55236 invoked by uid 500); 25 Mar 2009 08:59:13 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 55201 invoked by uid 500); 25 Mar 2009 08:59:13 -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 55193 invoked by uid 99); 25 Mar 2009 08:59:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Mar 2009 08:59:13 +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, 25 Mar 2009 08:59:12 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 5B2D2234C044 for ; Wed, 25 Mar 2009 01:58:52 -0700 (PDT) Message-ID: <1664427901.1237971532372.JavaMail.jira@brutus> Date: Wed, 25 Mar 2009 01:58:52 -0700 (PDT) From: "Knut Anders Hatlen (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Created: (DERBY-4117) dblook script fails when URL contains special characters 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 dblook script fails when URL contains special characters -------------------------------------------------------- Key: DERBY-4117 URL: https://issues.apache.org/jira/browse/DERBY-4117 Project: Derby Issue Type: Bug Components: Tools Affects Versions: 10.5.1.0 Reporter: Knut Anders Hatlen Priority: Minor This problem was discovered when testing 10.5.1.0-RC1. The dblook shell script fails if the database URL contains characters that have a special meaning to the shell, even if those characters are properly escaped/quoted on the command line. Example: $ ./bin/dblook -d 'jdbc:derby:jar:(demo/databases/toursdb.jar)toursdb' ./bin/dblook[29]: eval: syntax error at line 1: `(' unexpected Connection attributes, like create=true, will be ignored because the semi-colon makes the script execute the setting of the connection attribute as a separate shell command: $ ./bin/dblook -d 'jdbc:derby:NewDatabase;create=true' -- Timestamp: 2009-03-25 09:54:56.169 -- Source database is: NewDatabase -- Connection URL is: jdbc:derby:NewDatabase -- appendLogs: false -- Note: At least one unexpected error/warning message was -- encountered during DDL generation. See dblook.log -- to review the message(s). In dblook.log: java.sql.SQLException: Database 'NewDatabase' not found. at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) ... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.