> 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.

Roman Rokytskyy