|
2015-03-04
| ||
| 19:21 | • Closed ticket [c28d7fe915]: IDataReader.GetOrdinal throws "No Current Row" plus 2 other changes artifact: 90bdf08187 user: mistachkin | |
|
2015-03-02
| ||
| 19:12 | • Ticket [c28d7fe915]: 4 changes artifact: a518c7e13a user: mistachkin | |
| 19:07 | Add tests for ticket [c28d7fe915]. check-in: 2166864f27 user: mistachkin tags: nextRelease | |
| 17:40 | The IDataReader.GetOrdinal method should not throw 'no current row' exceptions. Fix for [c28d7fe915]. check-in: 0bcca49374 user: mistachkin tags: nextRelease | |
| 17:30 | • Ticket [c28d7fe915] IDataReader.GetOrdinal throws "No Current Row" status still Open with 8 other changes artifact: 24b1a00f77 user: mistachkin | |
| 14:42 | • New ticket [c28d7fe915]. artifact: f16ccb4c51 user: anonymous | |
| Ticket Hash: | c28d7fe915ea6d483d9003cc3aae9c5de72ce865 | ||
| Title: | IDataReader.GetOrdinal throws "No Current Row" | ||
| Status: | Closed | Type: | Code_Defect |
| Severity: | Important | Priority: | Medium |
| Subsystem: | Data_Reader | Resolution: | Fixed |
| Last Modified: | 2015-03-04 19:21:46 | ||
| Version Found In: | 1.0.95.0 | ||
| User Comments: | ||||
anonymous added on 2015-03-02 14:42:38:
After upgrading to the latest 1.0.95.0, I noticed that when I make a call to Getordinal on the datareader, before a call to Read() (that is I am caching the ordinals before looping the result set) an exception is thrown. This works in 1.0.94.0. If I make the call after calling the Read() method it works. Michael mistachkin added on 2015-03-02 17:30:49: This will be fixed on trunk soon. The fix will be in the 1.0.96.0 release. mistachkin added on 2015-03-02 19:12:01: Fixed on the "tkt-c28d7fe915" branch. | ||||