adminjs-typeorm icon indicating copy to clipboard operation
adminjs-typeorm copied to clipboard

Primary Key not being named "id"

Open maievsm opened this issue 4 years ago • 2 comments

Describe the bug I'm using TypeORM, and there's a weird behavior when using an entity with a primary key not named "id". Adding a resource that has a relation to this entity will result in a success, but the resource wont be added at all.

Installed libraries and their versions admin-bro: 3.4.0 admin-bro/express: 3.1.0 admin-bro/nestjs: 1.0.0 admin-bro/typeorm: 1.4.0 typeorm: 0.2.30

Schema


@Entity()
export class Profile extends BaseEntity {
  @PrimaryColumn()
  user_id: string;

  @OneToMany(() => Photo, (photo) => photo.profile)
  photos: Photo[];
}

@Entity()
export class Photo {
  @PrimaryGeneratedColumn()
  id: number;

  @ManyToOne(() => Profile, (profile) => profile.photos)
  profile: Profile;
}

When adding a Profile, everything works properly. But when adding a Photo, you'll receive a success despite it not being added.

maievsm avatar Feb 18 '21 18:02 maievsm

I guess you want to say "When adding a Photo, everything works properly. But when adding a Profile, you'll receive a success despite it not being added."

As is Profile the entity with primary key different from "id".

Same problem here. Editing those entities is throwing an error 'duplicate key value violates unique constraint 'table_pkey''

francofadini avatar Jun 11 '21 19:06 francofadini

Does the problem still persist in the latest version of the adapter?

dziraf avatar Feb 24 '22 10:02 dziraf