Bug #74718 | WRONG ENTRY IN ONLINE CLUSTERJ DOC | ||
---|---|---|---|
Submitted: | 6 Nov 2014 18:32 | Modified: | 2 Mar 2015 17:46 |
Reporter: | Lakshmi Narayanan Sreethar | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Cluster: Cluster/J | Severity: | S3 (Non-critical) |
Version: | 7.3 | OS: | Any |
Assigned to: | Daniel So | CPU Architecture: | Any |
[6 Nov 2014 18:32]
Lakshmi Narayanan Sreethar
[2 Mar 2015 17:46]
Daniel So
The section of the ClusterJ manual that was being referred to in the original bug description (http://dev.mysql.com/doc/ndbapi/en/mccj-issues.html) has since been updated to read: TIMESTAMP: Currently, ClusterJ does not support the TIMESTAMP data type for a primary key field. So, it has been clarified that not TIMESTAMP is unsupported, but it is not supported for a primary key field. Thus, the manual is now correct.