Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: naming conventions for Oracle/Unix vs. SQL Server
Suzy - it isn't just MS_LAND that uses mixed-case. i've seen more than one
non-M$ shop take advantage of that in their namingConvetions. shell
scripts, perl, java, and even other non-M$ databases - Sybase on HP-UX for
example.
i do however agree with the rest of the posts - probably not a good idea in oracleLand ;)
funny how passionate some can be about small things like this. we had a rather heated debate on whether this:
try {
stuff();
more.stuff();
}
or this:
try
{
stuff();
more.stuff();
}
was to be in our java standards recently. FWIW, the former won out.
-----Original Message-----
Sent: Monday, July 29, 2002 12:39 PM
To: Multiple recipients of list ORACLE-L
Definately underscores, if simply just to break the habit of developers assuming that mixed-case means something outside of MS-land. While SQL-Server does allow/display/use objects in mixed-case format, forcing that into Oracle *can* be done, but it's a bad idea. The Oracle data dictionary stores object definitions upper-case, and allows those objects to be referenced in any mixed case.
Forcing object creation in Oracle as mixed-case is a DDL hack using "" around the object name. At which point, the object can only be accessed in the exact case it was created enclosed with "". For example
SQL> create table "Test" (id number);
SQL> desc test
ERROR:
ORA-04043: object "test" does not exist
SQL> desc "test"
ERROR:
ORA-04043: object "test" does not exist
SQL> desc Test
ERROR:
ORA-04043: object "test" does not exist
SQL desc "Test"
Name Null? Type
----------------- ----- ---------- ID NUMBER
> Paula_Stankus_at_doh.state.fl.us wrote:
>
> 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!
-- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Suzy Vordos INET: lvordos_at_qwest.com Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: STEVE OLLIG INET: sollig_at_lifetouch.com Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).Received on Mon Jul 29 2002 - 15:38:32 CDT