Change
Make backup/restore independent of the mysql command line tools
Issue description
Currently backup and restore use the mysql command line client to do their work. Consider alternatives, so that in a distributed setup (web server and mysql server separate), the web server does not rely on this tool.
Developer comments
Since the web server must have some db connection, it needs some mysql packages. If those contain the mysql command line client, the issue has low priority.
The backup file is now produced _without the use of mysqldump_. The table data is written into a single insert statement. I tried to put each record onto a different line to improve readability, but that lead to the MySQL server being "gone" on import. While this could be resolved by adjusting %max_allowed_packet%, i decided waive the better readability of the backup file.
The import is also done without forking command line mysql.
It is still possible to do everything with the command line tools by using the parameter "--exec" on the backup or restore commands. This is a life line in case problems arise with the new method.
|
Work sessions3
Start |
2012-11-17T16:28:13
|
End |
2012-11-17T18:47:12
|
Participant |
Robert Cerny
|
Start |
2012-11-18T09:56:12
|
End |
2012-11-18T12:11:09
|
Participant |
Robert Cerny
|
Start |
2012-11-18T13:21:04
|
End |
2012-11-18T14:37:28
|
Participant |
Robert Cerny
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.