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
If you explicitly name your table with a prefix, its name is used correctly in constraint names. For example:
e01_t
s vc20 /nn /unique
This produces the expected result of:
create table e01_t (
id number generated by default on null as identity
constraint e01_t_id_pk primary key,
s varchar2(20 char)
constraint e01_t_s_unq unique not null
);
However, if you use the #prefix setting to add the prefix, then primary key constraint correctly includes the e01 table prefix, but the unique constraint prefix does not.
t
s vc20 /nn /unique
#prefix: e01
This produces the unexpected result (missing the e01_ prefix in the unique constraint name:
create table e01_t (
id number generated by default on null as identity
constraint e01_t_id_pk primary key,
s varchar2(20 char)
constraint t_s_unq unique not null
);
The text was updated successfully, but these errors were encountered:
If you explicitly name your table with a prefix, its name is used correctly in constraint names. For example:
This produces the expected result of:
However, if you use the
#prefix
setting to add the prefix, then primary key constraint correctly includes thee01
table prefix, but the unique constraint prefix does not.This produces the unexpected result (missing the
e01_
prefix in the unique constraint name:The text was updated successfully, but these errors were encountered: