Bug #52141 Invalid serialization of a DataTable colums of type MySqlDateTime
| Submitted: | 17 Mar 2010 14:40 | Modified: | 28 Apr 2010 16:30 |
|---|---|---|---|
| Reporter: | Janaka Abeywardhana | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | Connector / NET | Severity: | S3 (Non-critical) |
| Version: | 6.1.1 | OS: | Windows (Windows XP SP3) |
| Assigned to: | Tony Bedford | CPU Architecture: | Any |
| Tags: | ADO.NET, dataset, MysqlDateTime, serialization | ||
[17 Mar 2010 14:40]
Janaka Abeywardhana
[18 Mar 2010 3:32]
Janaka Abeywardhana
Hi, Have looked into this in greater detail and basically understood that Allow Zero Datetime also controls this behaviour. when set to false the dataset serializes correctly. Details on my blog http://www.janaka.co.uk/2010/03/serialization-issue-with-mysqldatetime.html if interested. If anything better error messages and documentation is probably what is lacking. Sorry if I wasted anybodies time. Please close the bug at your discretion. Thanks
[7 Apr 2010 8:20]
Tonci Grgin
Hi Janaka and thanks for your report. I agree we should try better document this so assigning Tony to fix it.
[28 Apr 2010 16:30]
Tony Bedford
The documentation for connection string option Allow Zero Datetime has been clarified. (XML sources have been updated)
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.039 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.