On 2002.10.16 17:04:59 -0400 Roman Rokytskyy wrote:

> > Hmmm thinking about it marginally more... does the spec have
> > instructions for this? I'd prefer actually to start by trying an
> > exact match, and if that fails then try converting the input to
> > uppercase and trying again. I don't think we should need to
> > escape-quote case sensitive column names to get them to work.
>
> +1 for your idea but only if we strip starting and ending double
> quotes. Consider the case of auto-generated statements from some text
> description (like JBoss jaws.xml). They will have double quotes
> everywhere if configuration has them.

too many choices....

Well, if someone goes to the trouble of explicitly including the
double-quote I think it means they KNOW they want that case...

how about this:

If there are double quotes, remove and look only for exact match:

if there are no double quotes, look first for exact match, and if it fails
uppercase and look for exact match.

I guess even with this someone could argue that if they defined a column as
"COL1" they might not want col1 (no "") to match, but I'm not going to
argue that.

david jencks