|
From: SourceForge.net <no...@so...> - 2011-04-19 23:03:15
|
Bugs item #3011063, was opened at 2010-06-03 16:48 Message generated for change (Settings changed) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=3011063&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Database Group: v 2.3 Status: Open Resolution: None >Priority: 4 Private: No Submitted By: mediaf (mediaforest) Assigned to: Nobody/Anonymous (nobody) Summary: backup.php doesn't use customized table names Initial Comment: When trying to use the backup function (backup.php) I get the error message (partially in french) : DEBUG INFORMATION: Invalid query: La table 'postfix.alias_domain' n'existe pas (The table 'postfix.alias_domain doesn't exist) The reason is that backup.php contains an array called $tables which redefines the tables used. It should instead use $CONF['database_prefix'] and $CONF['database_tables'] which can be defined in config.inc.php. ---------------------------------------------------------------------- Comment By: mediaf (mediaforest) Date: 2010-06-23 15:40 Message: I usually make database backups using phpMyAdmin, so for me it isn't critical to have a working backup module inside postfixadmin. ---------------------------------------------------------------------- Comment By: Charles (libertytrek) Date: 2010-06-23 15:18 Message: Hi Christian, I use this all the time, and find it extremely useful to be able to simply click a button and save a dump of the current database on my workstation. I would beg you to keep it... but maybe just change it to use the mysqldump command for mysql databases, and pgdump for postgresql databases? ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2010-06-22 22:22 Message: In fact, it should use the table_by_key() function ;-) That said: backup.php isn't really maintained and does not work with PostgreSQL. IMHO mysqldump is the better way to do backups. I'm even thinking about removing backup.php from postfixadmin - better no backup feature at all (people _will_ then use mysqldump) than a possibly broken one that gives you a broken backup... What do you think? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=3011063&group_id=191583 |
