Case sensitivity in table and field names
From: Gary Cornelisse <gary_at_conduit-it.com>
Date: 8 Feb 2002 10:22:13 -0800
Message-ID: <44dde6c.0202081022.5800ed6c_at_posting.google.com>
We've been developing our PHP/MySQL application over the past 4 years. We've been looking into PostgreSQL and Oracle as two candidates for out first compatibility update. We naturally realized there would be differences, small and large, in structure, data-types and some differences in SQL standards compliance. However, we did not expect that PostgreSQL would be uppercase biased. In other words, PostgreSQL prefers lowercase table and field names. This becomes a problem since we've designed our system with field names like My_Field_Name. And in the sql statements, names with uppercase letters would have to be enclosed in single quotes.
Date: 8 Feb 2002 10:22:13 -0800
Message-ID: <44dde6c.0202081022.5800ed6c_at_posting.google.com>
We've been developing our PHP/MySQL application over the past 4 years. We've been looking into PostgreSQL and Oracle as two candidates for out first compatibility update. We naturally realized there would be differences, small and large, in structure, data-types and some differences in SQL standards compliance. However, we did not expect that PostgreSQL would be uppercase biased. In other words, PostgreSQL prefers lowercase table and field names. This becomes a problem since we've designed our system with field names like My_Field_Name. And in the sql statements, names with uppercase letters would have to be enclosed in single quotes.
We noticed that Oracle does not require special treatment of uppercase letters in names. We're still researching other db systems to develop a consensus. Is lowercase or mixed-case the norm? Do we spend all the time converting db structure and SQL statements to all lowercase letters just to be more cross-db compatible?
Thanks,