Kbase P3882: Can the U## fields be removed from Oracle to create case-sensitive fields and indices?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/10/2008 |
|
Status: Verified
GOAL:
Can the U## fields be removed from Oracle to create case-sensitive fields and indices?
GOAL:
Can the U##column-name fields / columns be removed from Oracle to create case-sensitive fields and indices?
GOAL:
Can I delete the U##column-name from Oracle to create case-sensitive fields and indices?
FACT(s) (Environment):
Oracle DataServer
Oracle
FIX:
Since ORACLE is case-sensitive by default, the DataServer Product (case insensitive by default) allows the user to set the attributes of a field so that it can recognize either case sensitivity or case insensitivity.
When a field is not case sensitive, Progress does not distinguish between uppercase and lowercase letters for that index when sorting or matching data. This feature makes data entry more flexible and easier for end users, since lowercase or uppercase versions of an index can be used. However, when there is a need to enforce an uppercase/lowercase distinction within the application, set the attribute to case sensitive.
You can not delete the fields without deleting the indices. If you want to create case-sensitive fields and indices, you must do the following;
1. Remove both the indices with the U## fields and the U## fields
2. Then recreate the indices using the regular field
3. After that, update to the schema holder by re-pulling the information from Oracle.