When creating a many to many, bidirectional
relationship, the relationship table name generated is
longer than what my database (postgres) supports. The
name is truncated and deployment proceeds without
Postgres seems to be truncating table names at 31
characters. The table name went from
Upon redeployment, however, the code doesn't find the
relationship table with its long name, so it attempts
to create it again. This will cause a SQL error since
the table actually already exists. This causes
(re)deployment to fail with *lots* of stack traces.
I've had to resort to shortening the names of the
relationship methods to get this to work.
This is somewhat related to bug #516835 but is more
serious. (At least for me!)
It seems to me the table names and column names need to
be pushed though a general name mangler so that these
sort of things don't happen.