Re: [Postfixadmin-devel] Upgrade question Postfixadmin 2.3
Brought to you by:
christian_boltz,
gingerdog
From: Christian B. <pos...@cb...> - 2009-11-19 23:20:44
|
Hello, Am Montag, 16. November 2009 schrieb aja-lists: > Simone Piccardi wrote: > > I had the same issue after running the upgrade script for a 2.2 > > database. > > > > It was solved just adding the quota column in the domain table > > after the maxquota column. Those things should not happen and qualify as bug ;-) (Un)fortunately I never saw this problem on my system. Do you still have a database dump of the old table (before upgrading)? If yes, please post it (just the table structure + content of the "config" table which should be one line). BTW: do you use MySQL or PgSQL? > I decided to put back a > backup and started upgrading again, that gave amongst others a > "config" table not found which could not be handled by the > upgrade.php Hmm, another thing I've never seen... What was the exact error message? Which query was executed at this time? (see upgrade.php?debug=1) Does your database user have permissions to create and alter tables? And, as above: a database dump would be helpful. Regards, Christian Boltz -- Bei etwas größeren Dingen mit 6stelligem Budget kommt gern mal "plötzlich" ein Onlineshop dazu. Oder ein Ticketsystem. So ganz von alleine. Gucki, ich bin eine kleine Kundenidee - ist das viel Arbeit? ;) [Ratti in suse-linux] |