RE: naming conventions for Oracle/Unix vs. SQL Server

[Mercadante, Thomas F]

Title: RE: naming conventions for Oracle/Unix vs. SQL Server

Paula,

 

Someone will correct me if I'm wrong, but if you create tables and columns with mixed case within Oracle, then your developers will need to refer them surrounded by double quotes:  like:

 

SQL> create table "NameTable"("FirstName" varchar2(10));

 

Table created.

 

SQL> descr "NameTablee"
ERROR:
ORA-04043: object "NameTablee" does not exist

 

SQL> descr "NameTable"
 Name                                      Null?    Type
 ----------------------------------------- -------- -------------------
 FirstName                                          VARCHAR2(10)

 

SQL> select firstname from "NameTable";
select firstname from "NameTable"
       *
ERROR at line 1:
ORA-00904: invalid column name

 

SQL> select "FirstName" from "NameTable";

 

no rows selected

 

SQL>

 

 

Really Sucks!

 

Tom Mercadante
Oracle Certified Professional

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 29, 2002 11:59 AM
To: Multiple recipients of list ORACLE-L
Subject: RE: naming conventions for Oracle/Unix vs. SQL Server

Guys,

Please help.  I work in an organization where we have both SQL Server on NT and Oracle on Unix.  SQL Server and developers who are used to GUI's in NT like column names to have mixed case with no underscores.  The Unix folk - like myself prefer underscores and one case.  Is there any reason not to adopt mixed case for Oracle?  Is this really just what I am used to?  I have been using this standard for so long that it maybe the reasons I adopted it do not any longer exist or are not as compelling as developer's today are more comfortable with mixed case. 

Help!