You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we apply the migration to create the database table and indexes it generates:
-- Create table
create table A01ARQ01.ARQ_EMAIL_ADJUNTO
(
"Id" RAW(16) not null,
"NombreFichero" NVARCHAR2(255),
"Binario" BLOB,
"EmailId" RAW(16) default '00000000000000000000000000000000' not null
) tablespace ASSM_ARQAUD_DAT;
-- Create/Recreate indexes
create index INX_ARQ_EMAIL_ADJUNTO_01 on ARQ_EMAIL_ADJUNTO (EmailId) tablespace ASSM_ARQAUD_DAT;
-- Create/Recreate primary, unique and foreign key constraints
alter table ARQ_EMAIL_ADJUNTO
add constraint INX_ARQ_EMAIL_ADJUNTO_PK primary key (ID)
using index tablespace ASSM_ARQAUD_DAT;
alter table ARQ_EMAIL_ADJUNTO
add constraint FK_ARQ_EMAIL_ADJUNTO_ARQ_EMAIL_EmailId foreign key (EMAILID)
references ARQ_EMAIL (ID) on delete cascade;
It uses the default tablespace for the schema Our DBA demand to create index tablespaces in a different one
create index INX_ARQ_EMAIL_ADJUNTO_01 on ARQ_EMAIL_ADJUNTO (EmailId) tablespace ASSM_ARQAUD_IND;
and
alter table ARQ_EMAIL_ADJUNTO
add constraint INX_ARQ_EMAIL_ADJUNTO_PK primary key (ID)
using index tablespace ASSM_ARQAUD_IND;
The work around is not to use migrations and create the tables and index with SQL , the traditional way.
it's a shame that because of this feature we can't use migrations
For tables and indexes?
Thanks
The text was updated successfully, but these errors were encountered: