Error with MySQL and TRAC 0.12.4

[martin.fernholz@…]

I installed TracDirectoryAuth 0.5 with TRAC 0.12.4, MySQL 5.1.63 and AccountManager 0.3.2. After I activate the TracDirectoryAuth Plugin

tracext.adauth.api.userextensiblepermissionstore = enabled
tracext.adauth.auth.adauthstore = enabled
tracext.adauth.db.activedirectoryauthpluginsetup = enabled

and edit the trac.ini as at the projectpage shown I try to upgrade my project environment. Here I get this error message:

ProgrammingError: (1064, "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'varcahar(32),\n    `lut` int,\n    `data` binary,\n    PRIMARY KEY (`id`)\n)' at line 2")

Any idea what's wrong?

[anonymous]

I thinks it's invalid column type "varcahar". Fixed it and schema upgrade went smoothly.

[martin.fernholz@…]

Thx to "anonymous" for the silly hint. The error is in the file db.py in line 23. I tryed to update the source but I haven't a login for svn.

@sandinak: Please fix it.

Problem is fixed for me.

[Ryan J Ollos]

Replying to martin.fernholz@atm-computer.de:

@sandinak: Please fix it. Problem is fixed for me.

It is more likely to get fixed if you leave the ticket open until the issue is actually resolved in the codebase.

[Ryan J Ollos]

(In [12776]) Refs #10618: Fixed typo in database schema.

[Ryan J Ollos]

[12776] was reverted by the plugin author in [12971] and [12972], so the issue persists following r12972.

[anonymous]

This issue also reported in postgresql DB back end(Testing on trac 1.0 )

Run "trac-admin /opt/trac upgrade"

trac@trac:/etc/apache2/sites-enabled$ trac-admin /opt/trac upgrade
Error: Error reading '/opt/trac/conf/trac.ini', make sure it is readable.
trac@trac:/etc/apache2/sites-enabled$ sudo trac-admin /opt/trac upgrade
The upgrade failed. Please fix the issue and try again.

ProgrammingError: type "varcahar" does not exist
LINE 2:     "id" varcahar(32) PRIMARY KEY,
                 ^

[Ryan J Ollos]

(In [13074]) Fixes #10618: Fixed typo into DB schema. This had previously been fixed in [12776], but the change was reverted by the plugin author for unknown reason.