| Bug #7951 | Error reading a timestamp column | ||
|---|---|---|---|
| Submitted: | 17 Jan 2005 5:31 | Modified: | 1 Jun 2005 5:26 |
| Reporter: | Kris Kimbrough | ||
| Status: | Closed | ||
| Category: | Connector/Net | Severity: | S3 (Non-critical) |
| Version: | 1.0.3 | OS: | Microsoft Windows (Win/XP) |
| Assigned to: | Reggie Burnett | Target Version: | |
[17 Jan 2005 5:31]
Kris Kimbrough
[17 Jan 2005 19:52]
Reggie Burnett
Can you tell me what version of MySQL you are using? ALso, can you pinpoint the row that is causing the problem and give me the values of the columns you think are causing the problem?
[19 Jan 2005 5:56]
Kris Kimbrough
I am using MySQL 4.0.23 on windows/xp a sample value from the column (as reported by 3rd party tool MySQL-Front): 1/14/2005 7:33:16 AM I tried taking a timestamp value I am able to read from one table and updating a sample row in the larger table I'm having troubles with. This doesn't help, so I think it isn't just a simple parsing issue.
[24 May 2005 23:04]
Reggie Burnett
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.
If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information
about accessing the source trees is available at
http://www.mysql.com/doc/en/Installing_source_tree.html
[1 Jun 2005 5:26]
Paul DuBois
Noted in Connector/NET 1.0.5 changelog.
