| Anonymous | Login | Signup for a new account | 02-09-10 22:00 GMT |  |
| Main | My View | View Issues | Change Log | Roadmap |
| View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
| 0014509 | phplist | Message Management | public | 13-05-08 16:13 | 13-05-08 16:16 | ||||||
| Reporter | electrawn | ||||||||||
| Priority | normal | Severity | tweak | Reproducibility | always | ||||||
| Status | new | Resolution | open | ||||||||
| Platform | OS | OS Version | |||||||||
| Product Version | 2.10.5 | ||||||||||
| Target Version | 2.11.X | Fixed in Version | |||||||||
| Summary | 0014509: message table repeatuntil timsetamp set to '0000-00-00 00:00:00' instead of null | ||||||||||
| Description | When the message table edits a message, the repeatuntil timestamp field will get set to '0000-00-00 00:00:00' instead of null. This causes havoc when accessing the data via other methods such as JDBC or ODBC. MySQL will not convert a 0 timestamp to null unless a specific driver option is enabled (zeroDateTimeBehavior=convertToNull). I'll have time to trace this down later in the month and post a patch before June. | ||||||||||
| Tags | No tags attached. | ||||||||||
| Attached Files | |||||||||||
 Relationships |
|
 Relationships |
|
Notes |
|
| There are no notes attached to this issue. |
|
Notes |
