roblinx
asked on
Using mixed case for table and column names
We're used to developing systems for MS-SQL, and our standards have grown up around using mixed case identifiers--tables and columns--as allowed in MS-SQL. We have a new project that is using an Oracle back-end, and we're discovering that our standards don't play so well in the Oracle world. Mixed-case seems to be allowed, but it seems that our queries will have to make extensive use of double-quotes to accommodate this.
Can someone please summarize (or point me to) some current object naming standards for Oracle development work? Thank you in advance!
Can someone please summarize (or point me to) some current object naming standards for Oracle development work? Thank you in advance!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Use UPPER, LOWER functions to handle the case for upper and lower.
ASKER
Thanks guys... all very helpful!
What I'm looking for is opinions about best practices. We had gotten it into our heads (thanks to MSSQL work) that all-caps is bad, and underscores were wasted space. But... if Oracle requires the use of double-quotes to make use of mixed case for table and column names, perhaps it's not worth it.
What do you do when developing applications for Oracle databases? Mixed-case, or all caps?
What I'm looking for is opinions about best practices. We had gotten it into our heads (thanks to MSSQL work) that all-caps is bad, and underscores were wasted space. But... if Oracle requires the use of double-quotes to make use of mixed case for table and column names, perhaps it's not worth it.
What do you do when developing applications for Oracle databases? Mixed-case, or all caps?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks, experts, for your opinions and advice!
We ended up going against our MS-SQL background, using all-caps table and field names that employed underscores to separate words, where there was more than one word.
Examples:
BUSINESS_FUNCTIONS
USER_DIVISION_XREF
DIVISION_ID
CREATED_BY
I spread the credit around, as I did read and benefit from your answers. Thank you.
We ended up going against our MS-SQL background, using all-caps table and field names that employed underscores to separate words, where there was more than one word.
Examples:
BUSINESS_FUNCTIONS
USER_DIVISION_XREF
DIVISION_ID
CREATED_BY
I spread the credit around, as I did read and benefit from your answers. Thank you.
ASKER