Closed davemckain closed 10 years ago
This was fixed in commit 6737dd7, along with other potential name clashes taken from the list in [1].
NB: If you have an existing QTIWorks installation then you'll need to update your schema. There's a migration script (for PostgreSQL) in support/schema-migrations/beta5-to-beta6.sql
I'm not planning any more DB changes before the release of 1.0.0 final.
One of the mapped database column names 'public' specified in the JPA annotations is a reserved word in Microsoft SQL Server, so is causing problems there.
This will need to be renamed. It would be worth checking all other mappings too to ensure they're not reserved in any of the most common DB products.
(Note that existing installations will need to make a schema change once this has been fixed.)
Thanks to Kevin Curley for pointing this out.