Bug #4450 | create/drop table not propagated | ||
---|---|---|---|
Submitted: | 8 Jul 2004 2:08 | Modified: | 5 Oct 2004 11:07 |
Reporter: | Devananda v | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
Version: | 4.1.3 | OS: | Linux (Mandrake 9.2) |
Assigned to: | Magnus Blåudd | CPU Architecture: | Any |
[8 Jul 2004 2:08]
Devananda v
[8 Jul 2004 2:09]
Devananda v
(misspelled propagated)
[8 Jul 2004 7:14]
Jonas Oreland
Is it not sufficient to do a "select * from T" and the table will (dis)appear on the second mysql server?
[8 Jul 2004 8:58]
Martin Skold
NDB Cluster stores meta-data in the database, in contrast to the MySQL instance that stores it on the local file system. When an unknown table is specifically referenced in a query there is a discovery function that queries the cluster and copies meta-data to the querying MySQL instance. SHOW TABLES currently does not ask the cluster, this is a known shortcoming/fault, and it is planned to be fixed later. Also the creation of new databases is currently also not propagated between MySQL instances.
[5 Oct 2004 11:07]
Magnus Blåudd
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release. If necessary, you can access the source repository and build the latest available version, including the bugfix, yourself. More information about accessing the source trees is available at http://www.mysql.com/doc/en/Installing_source_tree.html