Bug #91199 | "Incorrect datetime value" attempting to use a MySqlDateTime as a parameter | ||
---|---|---|---|
Submitted: | 9 Jun 2018 20:38 | Modified: | 25 Jul 2018 3:42 |
Reporter: | Bradley Grainger (OCA) | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | Connector / NET | Severity: | S2 (Serious) |
Version: | 8.0.11 | OS: | Windows (10) |
Assigned to: | CPU Architecture: | x86 (x64) |
[9 Jun 2018 20:38]
Bradley Grainger
[11 Jun 2018 6:46]
Chiranjeevi Battula
Hello Bradley Grainger, Thank you for the bug report. This is most likely duplicate of Bug #80011, please see Bug #80011 Thanks, Chiranjeevi.
[11 Jun 2018 14:31]
Bradley Grainger
I don't know that this is exactly the same bug. In bug #80011 he says he's using the en-GB locale and adding DateTime.Now. In this example, I'm running in the en-US locale and adding new MySqlDateTime(DateTime.Now). I explicitly said that adding a new DateTime works fine, but that MySqlDateTime was broken; bug #80011 makes no mention of MySqlDateTime.
[25 Jul 2018 3:42]
Bradley Grainger
Chiranjeevi Battula, I really think this is a different issue, directly related to (or caused by) using a MySqlDateTime as a MySqlParameter value. A recent Stack Overflow question shows someone running into a variant of this exact problem: https://stackoverflow.com/q/51489520 Can this case be reopened?