unsupported driver -> Scan pair: <nil> -> *time.Time about mysql HOT 10 CLOSED

So are these fields NULL ?

from mysql.

It's a database/sql issue, which provides no NullTimeValue.
Have a look at issue #9 (esp. the part The driver gets no information about the destination type).

from mysql.

Yes it's NULL. As for not being able handle this kind of renders the time.Time support useless? Unless there is some workaround that does indeed use the recently added support for time.Time as oppose to manual string conversion.

from mysql.

You could make the timestamp non-null in the table and use a "marker time". It could even be faster that way.
I know, this advice sucks - but database/sql is not that good at supporting NULLable columns (yet?).

from mysql.

I'll add a NullTime type to the driver later

from mysql.

Just for reference:
The PostreSQL driver uses this NullTime

from mysql.

Thanks for that bit of info.. but I really am not sure how to implement this so I will just wait for an official fix to this repo and in the meantime will make the mysql field as non-NULL. This defaults to 0000-00-00 00:00:00

from mysql.

That was intended as a reference for whoever implements NullTime (probably Julien), not for users of the driver 😀 .

from mysql.

*Juli_e_n
See #63 ;)

from mysql.

Your issue would be...? (thank the Octocat for the edit function...)

from mysql.