Kbase P106048: Why no u##column with OE10 ORACLE DataServer?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Unverified
GOAL:
Why no u##column with OE10 ORACLE DataServer?
GOAL:
Problems with earlier u##columns when running OE10 ORACLE DataServer?
GOAL:
Change in OE10 for migration from ORACLE to Progress of case-insensitive index
FIX:
Starting with OpenEdge 10, support of case-insensitive indexes for ORACLE DataServer is done by using the UPPER(column_name) function as an index component. Existing case-insensitive indexes based on u##columns are still valid and you should not experience any problem.