The 'create index' migration with a prefix: mike option emits a statement like
create index tab_col on mike.tab (col)
but dropping it emits
drop index mike.tab_col
And depending on the username that is used in the connection, that actually makes a difference.
This can cause a 'name already used error', as the index is apparently create under the logged in user, ignoring the prefix:
create index tab_col on mary.tab (col)
create index tab_col on mike.tab (col) -- fails
The 'create index' migration with a
prefix: mike
option emits a statement likebut dropping it emits
And depending on the username that is used in the connection, that actually makes a difference. This can cause a 'name already used error', as the index is apparently create under the logged in user, ignoring the prefix:
I suggest to add the prefix like so
In
jamdb_oracle_sql.ex
that is easily done byboth in
execute_ddl
for theIndex :create
, and for theIndex :rename
case.That would make it consistent with
drop index
and also avoid the name clash.