Bug #53108 | Log group and table space create info not filtered out by "mysqldump --no-create | ||
---|---|---|---|
Submitted: | 23 Apr 2010 11:45 | Modified: | 23 Apr 2010 11:47 |
Reporter: | Hartmut Holzgraefe | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Cluster: Disk Data | Severity: | S3 (Non-critical) |
Version: | mysql-5.1-telco-7.0 | OS: | Linux |
Assigned to: | CPU Architecture: | Any | |
Tags: | all?, mysql-cluster-7.0.13 |
[23 Apr 2010 11:45]
Hartmut Holzgraefe
[16 May 2010 18:00]
Andrew Hutchings
You need --no-tablespaces for this: shell> mysqldump -uroot --no-tablespaces test -- MySQL dump 10.13 Distrib 5.1.44-ndb-7.1.3, for unknown-linux-gnu (x86_64) -- -- Host: localhost Database: test -- ------------------------------------------------------ -- Server version 5.1.44-ndb-7.1.3-cluster-gpl /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; /*!40101 SET NAMES utf8 */; /*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */; /*!40103 SET TIME_ZONE='+00:00' */; /*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */; /*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */; /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; /*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */; /*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */; /*!40101 SET SQL_MODE=@OLD_SQL_MODE */; /*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */; /*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */; /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */; /*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */; -- Dump completed on 2010-05-16 18:56:41 I guess it could be argued that --no-create-info should do this too. If it is decided that is correct behaviour it should be very easy to implement.
[17 May 2010 9:14]
Geert Vanderkelen
I guess the --no-tablespaces option is valid 'workaround'. IMHO, --no-create-info should indeed not dump anything related to DDL, except when asked for (using --no-create-info --all-tablespaces).