TypeOrm:使用uuid数据类型(而不是整数)为密钥创建ManyToOne关系

时间:2019-01-20 20:52:25

标签: node.js postgresql typescript nestjs typeorm

我有一个使用TypeORM和PostgreSQL数据库的Typescript Nestjs项目,并且我很难定义多对一关系,因为TypeORM尝试创建整数类型的ID字段,而我正在使用UUID字段。有没有办法告诉TypeORM使用不同于整数的数据类型?

这是一个无法正常工作的实体的示例:

export class AgentKitsEntity implements Model {
  @PrimaryGeneratedColumn()
  @Generated('uuid')
  id: string;
}

@Entity({name: 'users'})
export class User extends AgentKitsEntity implements UserModel {
  @Column()
  username: string;

  @ManyToOne(type => View)
  @JoinColumn({name: 'view_id', referencedColumnName: 'id'})
  view: View;
}

这会导致以下错误:

query failed: ALTER TABLE "users" ADD CONSTRAINT "FK_2ed8b186dce83a446f94ac9aae4" FOREIGN KEY ("view_id") REFERENCES "views"("id")
error: { error: foreign key constraint "FK_2ed8b186dce83a446f94ac9aae4" cannot be implemented
    at Connection.parseE (/home/jonathan/projects/agent-kits/api-data/node_modules/pg/lib/connection.js:554:11)
    at Connection.parseMessage (/home/jonathan/projects/agent-kits/api-data/node_modules/pg/lib/connection.js:379:19)
    at Socket.<anonymous> (/home/jonathan/projects/agent-kits/api-data/node_modules/pg/lib/connection.js:119:22)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at addChunk (_stream_readable.js:263:12)
    at readableAddChunk (_stream_readable.js:250:11)
    at Socket.Readable.push (_stream_readable.js:208:10)
    at TCP.onread (net.js:601:20)
  name: 'error',
  length: 228,
  severity: 'ERROR',
  code: '42804',
  detail: 'Key columns "view_id" and "id" are of incompatible types: integer and uuid.',
  hint: undefined,
  position: undefined,
  internalPosition: undefined,
  internalQuery: undefined,
  where: undefined,
  schema: undefined,
  table: undefined,
  column: undefined,
  dataType: undefined,
  constraint: undefined,
  file: 'tablecmds.c',
  line: '6503',
  routine: 'ATAddForeignKeyConstraint' }

编辑:只是要清楚,问题不是为主键创建UUID字段,这是可行的。问题是我要引用的表(在本示例中为“ views”)使用UUID主键,因此我也需要为引用该表的字段(在本示例中为“ views”)使用UUID。 TypeORM自动创建具有整数类型的“ view_id”字段,大概是因为它假定主键值将(应该?)始终为整数(这让我感到非常疯狂)。

它必须以某种方式可配置,不是吗?

1 个答案:

答案 0 :(得分:1)

我最终找到了解决方案,并将其发布在这里供以后参考。

以下对我有用:

export class AgentKitsEntity implements Model {
  @PrimaryGeneratedColumn('uuid')
  @Generated('uuid')
  id: string;
}

@Entity({name: 'users'})
export class User extends AgentKitsEntity implements UserModel {

  @Column()
  username: string;

  @ManyToOne(type => View, { nullable: true })
  @JoinColumn({name: 'view_id'})
  view: View;
}

似乎解决的关键区别是我在@PrimaryGeneratedColumn()装饰器中指定了'uuid'。这是令人惊讶的,因为实际上在数据库中已将字段正确地创建为UUID,但是除非您显式指定类型,否则TypeORM似乎将键字段假定为整数,即使该字段足够了解如何创建正确的数据也是如此。字段本身的类型。

编辑:仔细研究,结果发现@Generated('uuid')实体是多余的,因此上述基类的代码可以简化为:

export class AgentKitsEntity implements Model {
  @PrimaryGeneratedColumn('uuid')
  id: string;
}