Bug #2382
Improve format string error handling in ADD-NEW-FIELD implementation
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
08/28/2014
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
History
#1 Updated by Vadim Nebogatov almost 10 years ago
- File vmn_upd20140828c.zip added
Attached tests for different data types reproducing some errors.
decimal, integer
errors with different combinations of '<', '>', '.'
only 'z' is allowed, not 'Z'
date
errors with spaces
datetime
not supported.
Tomorrow I will attach draft code update fixing some of these errors.
#2 Updated by Vadim Nebogatov almost 10 years ago
Some additional problems with date
type:
1) IllegalStateException at DynamicTablesHelper:797
(missed date and datetime cases)
2) NumberedException: The month of a date must be from 1 to 12
at date:3955) because null format value is used.
#3 Updated by Vadim Nebogatov almost 10 years ago
- File vmn_upd20140912a.zip added
Attached draft intermediate update vmn_upd20140912a.zip with some fixes based on previous local changes.
#4 Updated by Vadim Nebogatov over 9 years ago
- File vmn_upd20141011b.zip added
Updated test cases vmn_upd20141011b.zip
attached. Only one file date_error_field_format.p
was updated and used for testing #2407.