Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Date: Tue, 13 Sep 2005 13:30:58 -0700
From: Rick Hillegas <Richard.Hillegas@Sun.COM>
Subject: Re: Side effects of quoting all column names in "CREATE TABLE"
 statement?
In-reply-to: <432723DC.6060202@bristowhill.com>
To: Derby Development <derby-dev@db.apache.org>
Message-id: <43273702.90302@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
References: <432723DC.6060202@bristowhill.com>

Hi Jean,

I certainly agree that it could prove very frustrating to someone 
banging ad hoc queries into a sql interpreter. However, it could work 
for an application if all queries come out of a code generator. It 
addresses the author's concern: it helps the engineer working in the sql 
portability layer of the application who has to struggle with the fact 
that reserved keywords vary among databases. It could also be useful for 
an IDE which lets developers give columns descriptive names that include 
illegal characters like spaces.

Just some random thoughts. :)

Cheers,
-Rick

Jean T. Anderson wrote:

> I've been lurking on ddlutils-dev@db.apache.org and spotted this issue 
> come through:
>
> http://issues.apache.org/jira/browse/DDLUTILS-15
>
> The suggestion is to quote all column names in the table create. But I 
> think that thereafter the user would always have to retain those 
> quotes unless he or she happened to enter the object name in upper 
> case, right? At a minimum, that would need to be documented.
>
> any opinions?
>
> thanks,
>
>  -jean
>