upgrade_2.0.5.sql

[caged_penguin]

Just a note, the upgrade 2.0.5 isn't very good.

I'm having to make modifications to make it run so I can upgrade vicidialnow 1.1's 2.0.4 to 2.0.5

Anyway that could be examined more fully?

Thanks!

[mflorell]

any specific Errors?

There are some purposeful errors in that file that will be removed upon official release of 2.0.5.

[caged_penguin]

It's the lines with alter table *_log DROP INDEX uniqueid;

Those lines..

There was one other.. But I can't remember.. Some of them I tried adding
IF EXISTS, But then I got worried that doing the upgrade without the sql file going cleanly might mess it up.
All I can ask is for you to setup a virtual machine with vicinow and then try to do the upgrade
to the vicidial svn trunk version to see.

Best Regards,
Danny Williams JR.
Act As One Technologies.

[mflorell]

Some of the errors you see depend on the version of MySQL you use and how they tread indexes differently. Through 2.0.5 we will maintain compatibility with MySQL 4.0.X which leads to some differences in how the database operates if you use MySQL 5.0.X. Once 2.0.5 is released we will drop MySQL 4.X compatibility in the development trunk branch which should allow us to do some things that were previously impossible under MySQL 4.X.

In short, those errors are normal.

[caged_penguin]

Alright, that explains that.. the mysql 4x vs the 5x factor.

Kewl.

Thanks Matt.