Bug #23550 | tool for converting offline from old ISAM format | ||
---|---|---|---|
Submitted: | 23 Oct 2006 11:49 | Modified: | 23 Oct 2006 21:16 |
Reporter: | sean finney | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: MyISAM storage engine | Severity: | S4 (Feature request) |
Version: | all | OS: | Any (all) |
Assigned to: | CPU Architecture: | Any |
[23 Oct 2006 11:49]
sean finney
[23 Oct 2006 12:15]
Hartmut Holzgraefe
verified as a feature request, but i'd recommend that you post this to the mysql mailing list(s), too ...
[23 Oct 2006 14:47]
Sergei Golubchik
You can try to create an utility from an old mysqld binary and a wrapper script to run it with --skip-networking --skip-privilege-tables --bootstrap There will be no need for a chroot jail, as mysqld won't daemonize, won't create a unix socket, won't listen to network - it'll only accept SQL from stdin. See how mysql_install_db does it.
[23 Oct 2006 21:16]
sean finney
hi sergei, harmut, i'll see about taking the issue to the lists, and in the meantime have sketched out a rough idea of how the 'chroot method' in the hopes that one of the debian bug reporters could give it a try and help lighten my workload a bit :) wrt the binary wrapper: unfortunately that just won't work due to the logistics of how debian distributes software. unless i could compile the wrapper from code in the latest tarball (or if it could be easily patched in), there isn't much that can be done to have a previous version of the binary installed. thanks for looking at this, sean
[23 Oct 2006 21:16]
sean finney
s/harmut/hartmut/, sorry :)
[10 Mar 2023 9:48]
Stefan Heisl
From what I understand, error #23550 suggests the want for an independent ISAM conversion device in the current model of MySQL. It appears that the old-fashioned ISAM structure has prompted issues for many customers who upgrade their servers due to new distribution variations or security updates. The proposed answer is to provide a utility that can operate offline ISAM conversion. One possible solution is to create a tool from an historic mysqld binary and a shell script that runs with specific options. However, this may additionally not be a workable option for Debian customers due to software distribution logistics. To tackle this problem, MySQL should consist of a standalone ISAM conversion tool inside the software that can be used to convert the out of date ISAM format to the more moderen MyISAM format. This tool need to be easy to use and platform-independent to make certain maximum compatibility with quite a number systems. Additionally, clear documentation and instructions ought to be provided to allow users to swap from ISAM to MyISAM without encountering any issues. Tutorial: https://andersenlab.com/industries/logistics