vicidial upgrade from 2.2 to 2.4 SVN in Goautodial

[gzpxyj]

I was trying to upgrade astguiclient to svn 2.4. It was OK for that part. But I do have questions about the sql portion. I might have run the sql upgrade twice and encountered some errors. It complains dulicate column names. quite a few such errors. Any issues about that or I might have to re-install it again for the database.

[gzpxyj]

When we upgrade from 2.2 to 2.4 svn trunk in Goautodial, the manual installation asked about the DB password, either 1234 or something you choose. I remembered in SQL password would be vicidialnow. Is this vicidialnow should be entered instead of 1234 of the default value?

[williamconley]

1) Always list your vicidial version with build (especially when discussing upgrades!)

2) you keep saying "password" but remember: it's not JUST password, it's user and pass. if you use the ROOT user, you'll need the ROOT pass to go with it. easily tested (mysql -p). if you are remembering the "cron" pass being 1234 ... remember that cron should not be able to modify the structure of the database ... so you should be using root instead when updating the mysql tables.

3) i've had many instances where a mysql command line fails during the upgrade. generally deleting the offending lines and all the lines before it (because they've already run) will suffice. usually it is the addition of a field or index already present or a removal of one that has already been removed. often you can check your dbschema value in system settings and remove any entries in the sql upgrade file that are earlier than that dbschema value (look for the dbschema upgrade sql command which occurs rather frequently).

but DO bring your brain: if the item that failed may be necessary, you may have to alter the query to allow it to work. i've not bumped into this recently, but it is possible.

when in doubt: bring the offending command HERE and ask