Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • But surely the person who created the table with inconsistently capitalized columns deserves some punishment as well? And why are case-sensitive column names worse than case-sensitive variable names or file names?
    • by djberg96 (2603) on 2004.08.04 17:58 (#33074) Journal
      And why are case-sensitive column names worse than case-sensitive variable names or file names?

      With variable names and file names, it's just easier to remember. With SQL, I'm constantly having to refer back to the column names to make sure I have them right. Also, we setup a transparent gateway with Oracle, but the case sensitivity means you have to wrap all of the column names in double quotes, so it's extra typing.

      That, perhaps, is a bit "fluffy", but I cannot think of a good reason to have case sensitive column names. I mean, are you really going to create two columns in the same table with the same name, differing only by case? Hell no! So, what's the point then? But, as jplindstrom points out (I think), it seems to be a generic setting that affects more than just column names.

      Oh, and on Windows, file names aren't case sensitive. :-P