Bug #86103 Wrong definition of exception table in doc
| Submitted: | 27 Apr 2017 3:32 | Modified: | 4 Aug 2017 9:44 |
|---|---|---|---|
| Reporter: | Mikiya Okuno | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Cluster: Documentation | Severity: | S3 (Non-critical) |
| Version: | 7.2+ | OS: | Any |
| Assigned to: | Jon Stephens | CPU Architecture: | Any |
[4 Aug 2017 9:44]
Jon Stephens
Fixed in mysqldoc rev 53270. Closed.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.039 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.
Description: The following table definition in the example is wrong: CREATE TABLE test.t2$EX ( server_id SMALLINT UNSIGNED, master_server_id INT UNSIGNED, master_epoch BIGINT UNSIGNED, count BIGINT UNSIGNED, a INT UNSIGNED NOT NULL, b CHAR(25) NOT NULL, [additional_columns,] PRIMARY KEY(server_id, master_server_id, master_epoch, count) ) ENGINE=NDB; CREATE TABLE test.t2$EX ( NDB$server_id SMALLINT UNSIGNED, NDB$master_server_id INT UNSIGNED, NDB$master_epoch BIGINT UNSIGNED, NDB$count BIGINT UNSIGNED, a INT UNSIGNED NOT NULL, NDB$OP_TYPE ENUM('WRITE_ROW','UPDATE_ROW', 'DELETE_ROW', 'REFRESH_ROW', 'READ_ROW') NOT NULL, NDB$CFT_CAUSE ENUM('ROW_DOES_NOT_EXIST', 'ROW_ALREADY_EXISTS', 'DATA_IN_CONFLICT', 'TRANS_IN_CONFLICT') NOT NULL, NDB$ORIG_TRANSID BIGINT UNSIGNED NOT NULL, [additional_columns,] PRIMARY KEY(NDB$server_id, NDB$master_server_id, NDB$master_epoch, NDB$count) ) ENGINE=NDB; How to repeat: n/a doc bug Suggested fix: Four columns at the beginning of exeption table must be: * INT UNSIGNED * INT UNSIGNED * BIGINT UNSIGNED * INT UNSIGNED Not: * SMALLINT UNSIGNED * INT UNSIGNED * BIGINT UNSIGNED * BIGINT UNSIGNED