Are you able to reproduce this in any fashion? It'd be interesting to
figure out why OpenJPA was attempting to recreate the indexes.
There are a couple of ways to get around the error:
- set the IgnoreErrors MappingTool flag to true. This will cause any
errors during schema synchronization to be
Note that I don't think OpenJPA reads index names from the existing
schema by default, so if you're adding fields or classes these might
be plain old naming conflicts due to truncation based on database
name length limits. There is a readSchema option on the mapping tool
that forces it to
Maybe I'm on crack, but
openjpa.jdbc.SynchronizeMappings=buildSchema(Indexes=false)
has no effect on 0.9.6 as I still see the CREATE INDEX statements
in the log. I am confident that my properties are being inspected
because when I set buildSchema(ForeignKeys=true, Indexes=false,