[Dbix-class] ENUM values from MySQL using the column_info()

[Matt S Trout]

Zbigniew Lukasiak wrote:
> On 5/13/06, Matt S Trout <dbix-class at trout.me.uk> wrote:
>> Ok. The debate was as to whether the column_info($col) stuff itself
>> could become case insensitive, which it can't. So long as you're only
>> lower casing stuff for the purposes of matching it up (and try a
>> case-sensitive match first so name/NAME works on DBDs that support
> 
> Hmm - so again we are at the point that I don't quite understand what
> you propose.  How should the trying case-sensitive match first work?
> I mean - if such a match fails how should I decide that I don't need
> to make a case-insensitive match?  And if you suppose that after that
> fail I should always try the other match than I don't see why should I
> try the case-sensitive match as it would not bring any additional
> information.

The point of the case-sensitive match is that *if* there are e.g. 
columns 'name' and 'NAME', and *if* the DBD returns separate column info 
for 'name' and 'NAME', the two column info chunks get matched to their 
appropriate columns correctly. Simple as that.