| Ticket Hash: | 52816622f3a38391f1a452d7b4780ca02e3a31dc | |||
| Title: | Data Rounding Issue with SQLiteDataAdapter | |||
| Status: | Closed | Type: | Incident | |
| Severity: | Important | Priority: | Medium | |
| Subsystem: | Data_Adapter | Resolution: | Works_As_Designed | |
| Last Modified: | 2014-07-09 15:14:10 | |||
| Version Found In: | 1.0.92.0 | |||
| User Comments: | ||||
anonymous added on 2014-07-02 18:13:57:
I run the same query using both the SQLiteCommand and SQLiteDataAdapter against a data set. The data set consists of: 0 1 2.6 3.3 3.5 4.3 and so on... Using SQLiteCommand, the query returns the proper values. But using SQLiteDataAdapter, it seems like it looks at the first value to determine the data type for the rest of the data. So using the sample data, my results are actually: 0 1 3 3 4 and so on... I have a sample project that replicates this behavior, but I cannot attach it using the ticket request. If you need me to add the project, please let me know where I can send it (through email is fine). Thank you for looking at this issue. anonymous added on 2014-07-02 18:16:42: I have attached the sample project to the ticket. mistachkin added on 2014-07-02 19:07:58: (text/x-fossil-plain) The data type appears to be "NUMBER$131$16,6,2"? How is this supposed to be interpreted? anonymous added on 2014-07-02 19:39:33: (text/x-fossil-plain) It's my own custom encoding just so I know what data to expect from that column. Basically taking advantage of the Typelessness feature. mistachkin added on 2014-07-02 21:06:57: (text/x-fossil-wiki) <verbatim>
This appears to be part of the design of how the .NET Framework handles data
adapters. Please insert the following line prior to the Fill() method call:
</verbatim>
<pre>
adapter.FillSchema(ds, SchemaType.Source);
</pre>
| ||||
