So to restate, without the readSchema option, the mapping tool
doesn't know the existing index names or which columns have indexes.
This means that indexes are created blindly, and there could very
well be an index conflict for an existing table created by OpenJPA.
Assuming that is true, shouldn't we change failed index creation
without readSchema to a warning instead of an error.
-dain
On Apr 2, 2007, at 10:15 AM, Abe White wrote:
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 read index and foreign key names and so forth, but
it slows the tool down a lot for some DBs with slow schema reflection.
Notice: This email message, together with any attachments, may
contain information of BEA Systems, Inc., its subsidiaries
and affiliated entities, that may be confidential, proprietary,
copyrighted and/or legally privileged, and is intended solely for
the use of the individual or entity named in this message. If you
are not the intended recipient, and have received this message in
error, please immediately return this by email and then delete it.
