Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <43ED9F61.1030605@Sourcery.Org>
Date: Sat, 11 Feb 2006 00:25:05 -0800
From: Satheesh Bandaram <satheesh@Sourcery.Org>
User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803)
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: Accept username  of form xyz@somedomain.com
References: <43ED2E1E.70100@gmail.com> <43ED4390.6070300@amberpoint.com>
In-Reply-To: <43ED4390.6070300@amberpoint.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


Bryan Pendleton wrote:

> Sunitha Kambhampati wrote:
>
>> If I try to connect, the error thrown is
>>    ij> connect
>> 'jdbc:derby:testdb;create=true;user=skambha@xyz.com;password=a';
>>    ERROR 28502: The user name 'skambha@xyz.com' is not valid.
>
>
> Is the string that we pass to "connect" an URL? If so, does it
> need to satisfy the URL character set requirements of RFC 1738:
> http://www.rfc-editor.org/rfc/rfc1738.txt

Also this authorizationID is currently used as SQL identifier. According
to ANSI, SQL identifiers can only have alphabets, digits and underscore.
That is why there seems to be that check. So, skamba@xyz.com is not a
valid SQL identifier.

You could treat them as delimited identifiers... meaning
'skamba@xyz.com', but that has its own issues.. User names need to be
case insensitive.

Satheesh