Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
How do I tell what character set Oracle is using 1
- Thread starter Tison
- Start date
-
1
- #2
SantaMufasa
Technical User
Tison,
1. Unlike other database-vendor products (example: Sybase, MS SQL Server, et cetera), Oracle is case-sensitive without choice. If you want Oracle to use case-insensitive comparison, you manually enforce case-insensitivity via your use of the UPPER(<expression>) or LOWER(<expression>) functions.
2. "select * from nls_database_parameters;"
Among the results will be:
NLS_CHARACTERSET <character_set>
Cheers,
Dave
1. Unlike other database-vendor products (example: Sybase, MS SQL Server, et cetera), Oracle is case-sensitive without choice. If you want Oracle to use case-insensitive comparison, you manually enforce case-insensitivity via your use of the UPPER(<expression>) or LOWER(<expression>) functions.
2. "select * from nls_database_parameters;"
Among the results will be:
NLS_CHARACTERSET <character_set>
Cheers,
Dave
dbalearner
Technical User
SantaMufasa,
FYI both Sybase and MSSQL are case sensitive when referencing objects on the command line OR within the data dictionary. Unlike Oracle, a command like "select * from MY_TABLE" results in error if MY_TABLE is created in lower case in Sybase, whereas this command would work fine in Oracle if table is created "my_table" or "MY_TABLE". So I would say Oracle data dictionary storage is case sensitive and Oracle command line reference is case insensitive.
FYI both Sybase and MSSQL are case sensitive when referencing objects on the command line OR within the data dictionary. Unlike Oracle, a command like "select * from MY_TABLE" results in error if MY_TABLE is created in lower case in Sybase, whereas this command would work fine in Oracle if table is created "my_table" or "MY_TABLE". So I would say Oracle data dictionary storage is case sensitive and Oracle command line reference is case insensitive.
SantaMufasa
Technical User
DBALearner,
I would agree that command-line processing in Oracle is generally forgiving (accepts/processes commands GENERALLY in either case). But, that is not the central issue when asserting that a database is "case sensitive" vs. "case insensitive".
In your previous post, you assert that '...this command would work fine in Oracle if table is created "my_table" or "MY_TABLE"...'. We need to be careful here, as the example below confirms:
create table "my_table" (x number);
insert into my_table values (1);
insert into my_table values (1)
*
ERROR at line 1:
ORA-00942: table or view does not exist
insert into "my_table" values (1);
select * from my_table;
select * from my_table
*
ERROR at line 1:
ORA-00942: table or view does not exist
select * from "my_table";
X
----------
1
Notice that Oracle command-line processing, by default, ASSUMES upper case. You can override that assumption with quotes. So, very literally, Oracle IS case sensitive, even in the data dictionary.
I would agree that command-line processing in Oracle is generally forgiving (accepts/processes commands GENERALLY in either case). But, that is not the central issue when asserting that a database is "case sensitive" vs. "case insensitive".
In your previous post, you assert that '...this command would work fine in Oracle if table is created "my_table" or "MY_TABLE"...'. We need to be careful here, as the example below confirms:
create table "my_table" (x number);
insert into my_table values (1);
insert into my_table values (1)
*
ERROR at line 1:
ORA-00942: table or view does not exist
insert into "my_table" values (1);
select * from my_table;
select * from my_table
*
ERROR at line 1:
ORA-00942: table or view does not exist
select * from "my_table";
X
----------
1
Notice that Oracle command-line processing, by default, ASSUMES upper case. You can override that assumption with quotes. So, very literally, Oracle IS case sensitive, even in the data dictionary.
- Status
Similar threads
- Locked
- Question
- Locked
- Question