| Ticket Hash: | 0550f0326eb5dd9ecd2572770e1bd60bf53ce1b2 | ||
| Title: | Regression: Wrong column sizes when "fixed-length" [3113734605] | ||
| Status: | Closed | Type: | Incident |
| Severity: | Important | Priority: | Blocker |
| Subsystem: | Connection | Resolution: | Fixed |
| Last Modified: | 2014-02-07 08:59:12 | ||
| Version Found In: | 1.0.89.0 | ||
| User Comments: | ||||
anonymous added on 2014-02-03 06:36:02:
Bug from Ticket 311373460518a9069b8a28f2fbacadd9a48ac203 reappeard in version 1.0.89.0. In the schema information the NumericPrecision attribute has the value of the ColumnSize and the ColumnSize attribute returns 2147483647 for string columns with a defined length mistachkin added on 2014-02-03 20:55:50: Do you have an example schema that demonstrates the issue? mistachkin added on 2014-02-04 21:00:18: Without further information from the opener, ticket will be closed on Thursday, February 6th, 2014. anonymous added on 2014-02-06 10:41:05: If you create a table like this "CREATE TABLE schema_test (first_column VARCHAR(150), second_column VARCHAR(150))" the problem occurs. With Version 1.0.84.1 the ColumnSize the schema information is 150, which is correct. In 1.0.89.0 the ColumnSize is 2147483647 and the NumericPrecision is 150 instead. I tested using CHAR(150) instead of VARCHAR(150) and this works correct in both versions. anonymous added on 2014-02-06 10:44:03: I meant version 1.0.84.0 and not 1.0.84.1 in my previous comment mistachkin added on 2014-02-06 19:18:22: Thanks for the test case. The issue was schema specific. Somehow, the AnsiString DbType was still not getting the correct handling. mistachkin added on 2014-02-06 19:45:36: Fixed on trunk via check-in [62a5b57a69]. mistachkin added on 2014-02-07 04:08:34: Issue introduced by check-in [c7b39f9c3b0df8d1]. | ||||