|
|
Posted by Erland Sommarskog on 10/02/72 11:47
Brian Peasland (oracle_dba@nospam.peasland.net) writes:
> So assume that you allow object names to be case sensitive. Then assume
> that you port from a RDBMS that allows this to an RDBMS that does not.
> You will run in to a problem trying to create that second Employees
> table no matter how it is spelled (case-wise). If you truly want to
> consider portability, you will make your object names different
> regardless of case.
Yes, having both "Employees" and "employees" in a database is bad idea.
That does not mean that it is a bad idea to have case-sensitive object
names. The issue you raise is fairly hypothetical.
The one that I and Tony raise is real. I can tell from own experience.
My main instances of SQL Server runs a case-sensitive collation. I
frequently copy scripts from newsgroup posts to help people find
solutions. I often have to spend quite some time of cleaning up
inconsistent case usage.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|