Hi Jesse,

I gather you started with OpenCollection 0.50 and then upgraded to 0.51? Did you have 0.50 running properly before upgrading?

The first error (1205) is an InnoDB lock timeout. It may have to do with the version of MySQL you are running (4.1, right?), or it may be a direct result of the second error you mention. In general, this error occurs when a MySQL transaction locks a table and fails to relinquish it. It is possible that the 1054 error is causing a transaction to dangle. I'll have to look into this.

One quick way to clear this sort of error when it happens (and it should not be happening very often, if at all) is to restart the database server. Not elegant, but it works.

Regarding the MySQL 1054 error, my guess would be that you did manage to properly update your version 0.50 database, but failed to update some of the application files to version 0.51. This would cause the error you are experiencing. In the near future we will be introducing an automated updater as the manual update procedure is definitely a pain.

If you could run the following SQL command on your database:

DESC object_phys_types;

and then post the output, that would be helpful.

If you need more real-time-ish help, drop me a line at info@opencollection.org and I'll be happy to work with you to resolve the problem.

seth