Not set Name Constraint > Unique

[SebaBoler]

Issue Description

I have @unique with name but in database name constraint have random value
Database : Postgresql 13

Expected Behavior

New Constraint with properly name from entity

Actual Behavior

Random name contraint

@ObjectType()
@Entity({ name: 'Event', schema: 'public' })
@Unique('UQ_EVENTSHORTNAME', ['eventShortName'])
@Index('idx_eventId', ['eventId'])
export class Event extends CoreEntity {
  @HideField()
  @PrimaryGeneratedColumn('increment')
  @Field(() => Int, { nullable: false })
  @IsInt()
  readonly eventId: number;

  @Field({ nullable: false })
  @Generated('uuid')
  @Column({ nullable: false })
  @IsUUID()
  readonly eventUUID: string;

  @Field(() => String, { nullable: false })
  @Column({ nullable: false })
  @MinLength(3, { message: 'Your eventShortName must be greater than 3' })
  @IsString()
  eventShortName: string;

Dependency	Version
Node.js version	16.9.1
Typescript version	4.0.5
TypeORM version	0.2.41

Relevant Database Driver(s)

Postgresql 13

[zoton2]

I also have this issue, only difference is I'm on PostgreSQL 12.4, but I imagine this is an issue in the library code and not the database side anyway.

Another note is, for me at least, this only happens if you're targeting one property, like in the example above, if you target multiple properties, it works fine.

There were older issues for this that were closed because it was assumed to be fixed by PR #7561, but that OP says...

Fixed @Unique constraint name behavior in SQLite. Looks like other drivers was already fixed because test is successfully passing.

...although 2/3 of the issues they linked were PostgreSQL, so I guess there were either issues with the tests, or something changed between then and current version (should try the older version myself and see). One of the issues mentions that dropping the table fully would fix it, but didn't test, and obviously a bit destructive. There's also a "workaround" posted here which can be used to find the constraint name so you can at least use it programatically.

[SebaBoler]

@zoton2 thank you for your reply. I used @Index

[Mordorreal]

@zoton2 This issue still exist for PostgreSQL 14.4

[neverovski]

@zoton2 thank you for your reply. I used @Index

@Index doesn't work for me. I need a constraint, not an index.

If you specify only one value in columnNames, typeOrm generates a random name. But you have more one values in columnNames, @unique works correctly

For example

Case 1:

export const UQ_CITY: UniqueOptions = {
  name: 'UQ_CITY',
  columnNames: ['name'],
};

typeorm generate sql command:

ALTER TABLE "cities" ADD CONSTRAINT "UQ_a0ae8d83b7d32359578c486e7f6" UNIQUE ("name");

Case 2:

export const UQ_CITY: UniqueOptions = {
  name: 'UQ_CITY',
  columnNames: ['name', 'countryId'],
};

typeorm generate sql command:

ALTER TABLE "cities" ADD CONSTRAINT "UQ_CITY" UNIQUE ("name", "countryId");

[VeniciusMarafon]

@zoton2
Any update? i have the same issue.

pg: 8.11.2
typeorm: 0.3.17

[TechGeorgii]

Same error, PostgreSQL 15.3, typeorm: 0.3.17