schema update problems (wrong case for table names)

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

stk137

Trying to install 2.1 (6/26) - upgrading  an existing 2.0 -
I get  "Schema auto-update failed"
and "Table 'alfresco.jbpm_task' doesn't exist"

well it does exist but it's just upper case, JPBM_TASK. 
Unfortunately, I'm currently stuck with case sensitive table names with MySQL/Linux.

While I can alter this update script, I can consider renaming my tables if Alfresco is assuming they are all lower case.

What is best for Alfresco in the long run?

It seems somewhat odd that the database Alfresco originally created is uppercase for JPBM_* tables and lowercase for afl_* tables.  Maybe the schema should just be created with all lower case if update scripts are going to make that assumption.

stk137

Hi,

Alfresco doesn't have anything to do with the case of table names.  In this case the scripts are generated by Hibernate, which generated the tables in the first place.  You'll notice in the logs, references to scripts that were generated.  Please post the following:

1. The entire contents of all the generated scripts.
2. Your exact JDBC driver version.
3. Your exact database version.

The case names of the tables have not been changed.  This is more than likely an issue with the database metadata generated by your particular JDBC driver and database being incorrect.  But we'll see. (http://bugs.mysql.com/bug.php?id=14848).

Regards

MySQL 5.0.27-standard
mysql-connector-java-5.0.3-bin.jar (with Alfresco 2.1 tomcat/common/lib)
mysql-connector-java-5.0.5-bin.jar (in my jre/lib/ext)
(not sure how to know which it used)

unfortunately, I don't have the update script anymore, is there an easy way to do a rollback and get it to regenerate?  This was 2.0 to 2.1.
When I looked at the script, there were not any schema changes so I just upper cased JPBM_TASK and ran the script without making a permanent copy (does Alfresco/Hibernate move that somewhere or just delete it?).  It looked like it just had some updates to say the patch had been applied.  So I wondered if those statements were from the hibernate schema-update generater or not.  I did find another thread about an issue like this with Hibernate,  but it was from 2.x and was supposed to be fixed in 3.x.

thanks,

Steve