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
In the near future, the probability is close to zero. In the distant
future, I'll be dead, and posterity can do whatever they like... :-) --lwall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Hmm (Score:2)
Re:Hmm (Score:2)
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
Reply to This
Parent