Skip to main content
Deno 2 is finally here 🎉️
Learn more
Module

x/typeorm/src/index.ts>RelationOptions

Forked from https://github.com/typeorm/typeorm
Latest
interface RelationOptions
Re-export
import { type RelationOptions } from "https://deno.land/x/typeorm@v0.2.23-rc10/src/index.ts";

Describes all relation's options.

Properties

optional
cascade: boolean | ("insert" | "update" | "remove")[]

Sets cascades options for the given relation. If set to true then it means that related object can be allowed to be inserted or updated in the database. You can separately restrict cascades to insertion or updation using following syntax:

cascade: ["insert", "update"] // include or exclude one of them

optional
nullable: boolean

Indicates if relation column value can be nullable or not.

optional
onDelete: OnDeleteType

Database cascade action on delete.

optional
onUpdate: OnUpdateType

Database cascade action on update.

optional
deferrable: DeferrableType

Indicate if foreign key constraints can be deferred.

optional
primary: boolean

Indicates if this relation will be a primary key. Can be used only for many-to-one and owner one-to-one relations.

optional
lazy: boolean

Set this relation to be lazy. Note: lazy relations are promises. When you call them they return promise which resolve relation result then. If your property's type is Promise then this relation is set to lazy automatically.

optional
eager: boolean

Set this relation to be eager. Eager relations are always loaded automatically when relation's owner entity is loaded using find* methods. Only using QueryBuilder prevents loading eager relations. Eager flag cannot be set from both sides of relation - you can eager load only one side of the relationship.

optional
persistence: boolean

Indicates if persistence is enabled for the relation. By default its enabled, but if you want to avoid any changes in the relation to be reflected in the database you can disable it. If its disabled you can only change a relation from inverse side of a relation or using relation query builder functionality. This is useful for performance optimization since its disabling avoid multiple extra queries during entity save.