| Ticket Hash: | 311373460518a9069b8a28f2fbacadd9a48ac203 | ||
| Title: | Schema information for column size is wrong in version 1.0.85 | ||
| Status: | Closed | Type: | Code_Defect |
| Severity: | Important | Priority: | Medium |
| Subsystem: | Data_Reader | Resolution: | Fixed |
| Last Modified: | 2013-08-29 07:11:55 | ||
| Version Found In: | 1.0.85.0 | ||
| User Comments: | ||||
anonymous added on 2013-08-28 12:33:49:
As as simple example, add a table with one field of type Char(3). Create a view that selects that column (Select * FROM table). If you look at the schema information on the results, you will see the ColumnSize is now reported as 2147483647. The NumericPrecision field is 3 now. In a previous version (1.0.84), it correctly reports 3 as the ColumnSize and the NumericPrecision field is blank. We rely on getting the correct field size from this query. Is this going to be a permanent change? Was this an intentional change going foward? mistachkin added on 2013-08-29 06:12:15: Issue confirmed. Working on fix. mistachkin added on 2013-08-29 07:11:55: Fixed on trunk by check-in [9531731b98]. This issue impacted the CHAR and NCHAR column types (with column sizes specified) and using VARCHAR or NVARCHAR (also with column sizes specified) is a workaround for the issue. | ||||