Creating a table with any index and @Unique fails on Oracle with ORA-01408

Description

We made the "silly" mistake of defining one field in one of our AO tables with both @Indexed and @Unique.

Every database but Oracle accepted this. Oracle failed with an error (ORA-01408: such column list already indexed) and throws an exception on every AO request (probably since migrate doesn't finish) and that made our plugin unusable on Oracle.

Shouldn't AO detect that a duplicate index is being created and stop the developer from doing this mistake?

Best regards,

-Bjarni

Environment

None

Testing Notes

None

Status

Assignee

Unassigned

Reporter

Bjarni Þorbjörnsson

Labels

None

Add-on Type

None

Team

None

CC

None

Risk factor

None

QA Kickoff Status

None

QA Demo Status

None

Components

Priority

Major
Configure