MySQL 5.6 new timestamp types need support in prep statement

Bug #1094538 reported by Andrew Hutchings
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Drizzle Client & Protocol Library
Invalid
Low
Unassigned

Bug Description

MySQL 5.6 has new timestamp types. Not sure what the format is yet as it isn't documented but we need to support it.

Revision history for this message
Wim Lewis (wiml-omni) wrote :

The mysql 5.6 docs at <http://dev.mysql.com/doc/refman/5.6/en/c-api-data-structures.html> say:

"The MYSQL_TYPE_TIME2, MYSQL_TYPE_DATETIME2, and MYSQL_TYPE_TIMESTAMP2 type codes are used only on the server side. Clients see the MYSQL_TYPE_TIME, MYSQL_TYPE_DATETIME, and MYSQL_TYPE_TIMESTAMP codes."

and a glance through the sources at lp:mysql-server doesn't show any protocol packing/unpacking code for those types, just for the usual ones.

Revision history for this message
Andrew Hutchings (linuxjedi) wrote :

ah ha! Thanks for looking into this, I just saw it in the types list and assumed they were actually used externally.

Changed in libdrizzle:
status: New → Invalid
Changed in libdrizzle:
milestone: none → 5.1.4
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.