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

use Perl Log In

Log In

[ Create a new account ]

djberg96 (2603)

djberg96
  (email not shown publicly)

Journal of djberg96 (2603)

Wednesday August 04, 2004
03:00 PM

Thought for the day #4

[ #20234 ]
Whoever made column names case sensitive in Sybase deserves a gruesome death.

List all Journal entries
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Thought for the day #4 4 Comments More | Login | Reply /

 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?
    • 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 sen

  • In Sybase you decide on sort-order when creating the dataserver (oracle-speak: instance, kind of). The sort-order can be case sensitive or insensitive.

    It's used for the sys% tables as well, which is why you have that problem.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.