The new patch :
- disables the 'dump # rows' and 'dump all rows' options on the export page
- checks if the table is not a view before checking the Engine (views don't have an Engine parameter)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
the patch applied cleanly to trunk. However, when testing with the sample MERGE table as explained on http://dev.mysql.com/doc/refman/5.1/en/merge-storage-engine.html and MySQL 5.1.40, the data of the MERGE table is still exported. Testing with on-screen export and with saving as file.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
New patch (rev. 3) was tested against MySQL 5.1.31 and 5.0.45 and now exports no data (in case of a merge table) in both MySQL versions.
Changes : The name of the merge table engine is changed in MySQL 5.1.x to MRG_MYISAM (is MRG_MyISAM until 5.0.x), patch (rev. 3) counters this.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
patch (rev. 2)
The new patch :
- disables the 'dump # rows' and 'dump all rows' options on the export page
- checks if the table is not a view before checking the Engine (views don't have an Engine parameter)
Hi,
the patch applied cleanly to trunk. However, when testing with the sample MERGE table as explained on http://dev.mysql.com/doc/refman/5.1/en/merge-storage-engine.html and MySQL 5.1.40, the data of the MERGE table is still exported. Testing with on-screen export and with saving as file.
patch (rev. 3)
New patch (rev. 3) was tested against MySQL 5.1.31 and 5.0.45 and now exports no data (in case of a merge table) in both MySQL versions.
Changes : The name of the merge table engine is changed in MySQL 5.1.x to MRG_MYISAM (is MRG_MyISAM until 5.0.x), patch (rev. 3) counters this.
Merged in subversion, thanks.