| Bug #67992 | The new MySQL 5.6 data types need documenting in internals | ||
|---|---|---|---|
| Submitted: | 30 Dec 2012 0:31 | Modified: | 7 Jan 2014 19:37 | 
| Reporter: | Andrew Hutchings | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) | 
| Version: | OS: | Any | |
| Assigned to: | Jan Kneschke | CPU Architecture: | Any | 
   [30 Dec 2012 0:31]
   Andrew Hutchings        
  
 
   [30 Dec 2012 6:21]
   MySQL Verification Team        
  Assuming you are referring to: MYSQL_TYPE_TIMESTAMP2 MYSQL_TYPE_DATETIME2 MYSQL_TYPE_TIME2
   [7 Jan 2014 19:37]
   Jan Kneschke        
  Thank you for taking the time to write to us, but this is not a bug. MYSQL_TYPE_TIMESTAMP2, MYSQL_TYPE_TIME2 and MYSQL_TYPE_DATETIME2 are internal types of the MySQL Server and are not used in the protocol. Instead the _TIMESTAMP, _TIME and _DATETIME types can have a optional sub-second field.

