hi!
from my experience of haveing the same data or data model
on different DB brands and platforms it is wise wiser wisest
- cause you never know what the management is going to
buy next - to stick to the following naming conventions
for identifiers:
+ all identifiers in uppercase
+ not more
Title: 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
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 "Name
The only way to insert a column name in mixed case with Oracle is to enclose
the create statements column names in double-quotes.. This also means that
when selecting from the created table, you have to enclose the mixed case
column name in double quotes as well.. Ad-hoc type queries could go
Title: RE: naming conventions for Oracle/Unix vs. SQL Server
Paula:
The mixed case for Oracle does not matter,
as Oracle is not case sensitive. The
column names are stored in uppercase within the data dictionary. However, for SQL Server, the case sensitivity
of column names is crucial
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
Title: RE: naming conventions for Oracle/Unix vs. SQL Server
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
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
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
I come from a Unix/Shell/Perl/Java background where exact case match is
important. Which is why it's s apparent that MS's lack of case
sensitivity bugs me :)
I recently had a similar discussion with a developer, who was absolutely
puzzled that case-sensitivity was an issue because his
respond to ORACLE-L
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
cc:
Subject:RE: naming conventions for Oracle/Unix vs. SQL Server
Paula:
The mixed case for Oracle does not matter, as Oracle is not case
sensitive. The column names are stored
10 matches
Mail list logo
