Using Class::DBI with Sybase and mixed case columns

rinceWind has asked for the wisdom of the Perl Monks concerning the following question:

Monks,

I'm having a problem with getting Class::DBI to talk to a legacy Sybase database. Unfortunately, the people who designed the application that uses said database, used studlyCaps for the column names (ugh! *****y C++ programmers :( ).

Using SQL from DBI works fine for me. I get back exactly what I expect. But it seems that Class::DBI insists on lowercasing all the column names, which are then rejected by Sybase SQL as invalid. Is Sybase the only database with case sensitive column names?

Is there a hook or a handle to persuade Class::DBI or Class::DBI::Sybase not to do this, and to present the column names as I have given them?

--
I'm Not Just Another Perl Hacker

Comment on Using Class::DBI with Sybase and mixed case columns

Replies are listed 'Best First'.
Re: Using Class::DBI with Sybase and mixed case columns by Joost (Canon) on Dec 24, 2004 at 20:44 UTC
There has been some talk about this behaviour on the cdbi-talk mailinglist recently. I don't know if the suggestions there are helpful for your case. If no-one here can give you a work-around, try asking on the cdbi-talk list. The people there are quite helpful. "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply]
Re: Using Class::DBI with Sybase and mixed case columns by jplindstrom (Monsignor) on Dec 26, 2004 at 18:04 UTC
This doesn't really solve your problem but... In Sybase you decide on sort-order and case when you install/configure the dataserver (not a particular database). This configuration then applies to the entire dataserver, including the system tables. So if your application data needs to be case sensitive, then the table names will be case sensitive too. At least this is how I understand the issue, I'm sure mpeppler can explain it in more detail :) /J	[reply]