因此,我想实现一个删除GraphNode
的{{1}}的{{1}}为id
的情况,然后将其重置为{{1 }}。
因此,我提出了以下建议:
图:
GraphNode
GraphNode:
startNodeId
错误:
null
因此,如果我现在将@Entity()
export class Graph extends BaseEntity {
@PrimaryGeneratedColumn('uuid')
public id: string;
@Column({ nullable: true })
public startNodeId?: string;
@ManyToOne(() => GraphNode, { onDelete: 'SET NULL' })
@JoinColumn({ name: 'startNodeId', referencedColumnName: 'id' })
public startNode: GraphNode;
}
添加到@Entity()
export class GraphNode extends BaseEntity {
@PrimaryGeneratedColumn('uuid')
public id: string;
@PrimaryColumn('uuid')
public graphId: string;
@ManyToOne(() => Graph)
@JoinColumn({ name: 'graphId' })
public graph: Graph;
}
上,它将起作用。但是No unique Unique-Constraint in the referenced table graphNode
已经具有@Unique(['id'])
装饰器。该用例是否有必要将GraphNode
定义为唯一?