Feature #1663
test/debug case-sensitive field support
Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
05/01/2013
Due date:
05/02/2013
% Done:
100%
Estimated time:
16.00 h
billable:
No
vendor_id:
GCD
Related issues
History
#1 Updated by Greg Shah over 11 years ago
- Target version set to Milestone 7
#2 Updated by Eric Faulhaber over 11 years ago
- Assignee set to Ovidiu Maxiniuc
This task is about defining temporary and permanent database tables with a mix of case-sensitive and case-insensitive character fields. The schema (along with any supporting artifacts, like dmo_index.xml) should convert properly. Queries referencing these fields in where clauses and by clauses should convert correctly and operate properly at run time.
#3 Updated by Eric Faulhaber almost 11 years ago
- Status changed from New to Closed
- Assignee changed from Ovidiu Maxiniuc to Eric Faulhaber
- Start date set to 05/01/2013
- % Done changed from 0 to 100
- Due date set to 05/02/2013
I've reviewed the schema and code conversion, and the runtime code. It appears case-sensitive fields are dealt with properly throughout.
#4 Updated by Greg Shah over 7 years ago
- Target version changed from Milestone 7 to Runtime Support for Server Features