-
If you create a table "Employee" then
select * from employee
You'll get ora-942 table or view does not exist
select * from "Employee" is the only way to address that table
Drop the double quotes.
If the software user is naming db objects, don't use double quotes!
-
First of all, SQLServer means case-sensitive *data*, not object names. You know - as opposed to Oracle, where the data is *always* (very unfortunately) case-sensitive.
I don't know of any database where the object names are case-sensitive.
You may want to do a little more digging into database details if you truly want to make a product that works across databases ( a really bad idea, IMHO )
- Chris
-
I have seen the 'case sensitivity' issue before, usually with software developped for multiple databases where the other database (say SQL Server) is case sensitive. Almost always the same situation (a software house with a canned project). I don't like it, but it is your coding headache.
As for the customer worry, why not just use a definition export as part of your installation process. Create the objects with case sensitivity, export the definitions (ROWS=N) and use that file for installation. If the client changes the installation procedure or objects afterward, they violated your support aggreement, yada yada yada.
As for the database, the Instance name may be case insensitive (depending on platform, release etc.) but the Oracle doesn't use databases the way other RDBMSs do. A SQL Server instance contains multiple databases which contain schemas. Oracle instances just contain schemas. SQL Server databases can be case sensitive but there is no corresponding object in Oracle.
Joseph R.P. Maloney, CSP,CDP,CCP
'The answer is 42'
-
jrpm - are you talking data or object names when you say you've seen the case-sensitivity issue before?
- Chris
-
Originally posted by chrisrlong
I don't know of any database where the object names are case-sensitive.
MS Access!
Jeff Hunter
-
Is that a database? Just kidding... well maybe not.
-
Originally posted by marist89
MS Access!
I just pulled up an Access database, changed the case of one of the object names in one of my queries and ran it and it still ran fine. What makes you think it's case-sensitive?
- Chris
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|