DateTime issue with MySQL Database

[adrianimboden]

I've found an issue when using multiple DateTime columns in a MySQL table.
The following code statement produces table content as stated below:

Poco::Data::Session sess("MySQL", "host=localhost;user=root;password=;db=mydb");
sess << "DROP TABLE IF EXISTS test;", now;
sess << "CREATE TABLE test (field1 DATETIME, field2 DATETIME)", now;
Poco::DateTime date(2013, 01, 02, 01, 02, 03, 4, 5);
sess << "INSERT INTO test (field1) VALUES(?)", use(date), now;
sess << "INSERT INTO test (field2) VALUES(?)", use(date), now;
sess << "INSERT INTO test (field1, field2) VALUES(?, ?)", use(date), use(date), now;

Table content afterwards:
| field1 | field2 |
| 2013-01-02 01:02:03 | NULL |
| NULL | 2013-01-02 01:02:03 |
| 0000-00-02 01:02:03 | 2013-01-02 01:02:03 |

The first two rows are as expected, but the last row is clearly malformed.

I'm using gcc 4.7.2 on Debian Wheezy and the mysqlclient library in version 5.5.28

[adrianimboden]

I decided to participate to this project a little bit too.
I found the bug that caused this problem. The bound parameter is being stored in a std::vector and a pointer to the internal structure of the vector is being used in the mysql library call.

I fixed it and a pull request is pending :)

[simfe]

how to resolve this bug ?
Thanks!

[simfe]

oh.I found where is the bug,and resolve it. and then,the latest poco develop version resolved it. we are the same.