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: domain of bpendleton.derby@gmail.com
 designates 209.85.160.44 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=Bn2yG9RMhfGZ0c2GDWe/HGW76gblM4EmG+p7VAKZiD2tyxRTCi2smls9y8Op/vbFXA
         4+5dmL7kywLNlZ7ecp9OtVzqcyXT9xSjMrKwozKOQasrn50//cQwx54Fxr+BzWyzlGUW
         kWx16AKxYMou4FPGmLeuzAf3qIJYNoJGc32PI=
Message-ID: <4C3DCF10.4080003@gmail.com>
Date: Wed, 14 Jul 2010 07:52:00 -0700
From: Bryan Pendleton <bpendleton.derby@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.9.1.10) Gecko/20100527 Thunderbird/3.0.5
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: SYSCS_UTIL.SYSCS_SET_XPLAIN_SCHEMA Error
References: <AANLkTimg-MgkJC5rAA0xJ7TArSE-tENUzj0ByrECZfJg@mail.gmail.com>
In-Reply-To: <AANLkTimg-MgkJC5rAA0xJ7TArSE-tENUzj0ByrECZfJg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

> ij> select stmt_id from 3892.sysxplain_statements;

Does this work:

select stmt_id from "3892".sysxplain_statements;

Probably not, I think that you are right that a schema name
cannot start with a digit.

> I think the error is probably due to use of an Integer instead of a
> Character as the starting character of schema name specified.
>
> If it's the case I guess we should not allow that when a user initiates
> the schema.

Yes I think you are right, this is a bug in the SET_XPLAIN_SCHEMA procedure.

Good catch!

Would you be willing to file it and investigate it?

thanks,

bryan