Kbase 16758: DSV Case sensitive = yes in data dict when case-insensitive
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
DSV Case sensitive = yes in data dict when case-insensitive
This kbase attempts to explain why the Data Dictionary
"case sensitive" field is set to yes when a field in an Oracle table
set to case-insensitive.
Oracle supports only case-sensitive indexes, but Progress allows you
to set the attributes of a field so that it is case-sensitive or case-
insensitive when using the Oracle dataserver. See the DataServer for
Oracle Guide for instructions.
When a field is set to case-insensitive the "case sensitive" field
in the data dictionary indicates to the dataserver that there are
two columns one case-sensitive and one case-insensitive which was set
to the uppercase value of the orginal column using the method outlined
in the dataserver manual. If there is an index defined on the column
the dataserver has to use the case insensitive shadow column (i.e the
U##..... field) in the index. "Case sensitive" set to "y" means that
the field is case-insensitive seems counter intuitive but for now it
is how it works.
ICK 3/24/97
Progress Software Technical Support Note # 16758