Skip to main content
Version: 7.0

Defining Entities

Entities are simple javascript objects (so called POJO) without restrictions and without the need to extend base classes. Using entity constructors works as well - they are never executed for managed entities (loaded from database). Every entity is required to have a primary key.

Entities can be defined in two ways:

  • defineEntity helper - Define entities programmatically with full TypeScript type inference. You can use it with a class (recommended) or without one. Read more about this in the defineEntity section.
  • Decorated classes - the attributes of the entity, as well as each property are provided via decorators. You use @Entity() decorator on the class. Entity properties are decorated either with @Property decorator, or with one of reference decorators: @ManyToOne, @OneToMany, @OneToOne and @ManyToMany. Check out the full decorator reference.

Moreover, how the metadata extraction from decorators happens is controlled via MetadataProvider. Three main metadata providers are:

  • MetadataProvider - default provider that only enforces the types are provided explicitly.
  • ReflectMetadataProvider - uses reflect-metadata to read the property types. Faster but simpler and more verbose.
  • TsMorphMetadataProvider - uses ts-morph to read the type information from the TypeScript compiled API. Heavier (requires full TS as a dependency), but allows DRY entity definition. With ts-morph you are able to extract the type as it is defined in the code, including interface names, as well as optionality of properties.

Read more about them in the Metadata Providers section. For a comprehensive guide on using decorators (including the new ES spec decorators in v7), see the Using Decorators guide. For glob-based entity discovery, see Folder-based Discovery.

Current set of decorators in MikroORM is designed to work with the tsc. Using babel and swc is also possible, but requires some additional setup. Read more about it here. For notes about webpack, read the deployment section.

ts-morph is compatible only with the tsc approach.

Example definition of a Book entity follows. You can switch the tabs to see the difference for various ways:

./entities/Book.ts
import { defineEntity, p } from '@mikro-orm/core';

const BookSchema = defineEntity({
  name: 'Book',
  extends: CustomBaseEntity,
  properties: {
    title: p.string(),
    author: () => p.manyToOne(Author),
    publisher: () => p.manyToOne(Publisher)
      .ref()
      .nullable(),
    tags: () => p.manyToMany(BookTag)
      .fixedOrder(),
  },
});

export class Book extends BookSchema.class {}
BookSchema.setClass(Book);

Including { ref: true } in your Ref property definitions will wrap the reference, providing access to helper methods like .load and .unwrap, which can be helpful for loading data and changing the type of your references where you plan to use them.

Here is another example of Author entity, that was referenced from the Book one, this time defined for mongo:

./entities/Author.ts
import { defineEntity, p } from '@mikro-orm/core';

const AuthorSchema = defineEntity({
  name: 'Author',
  properties: {
    _id: p.type(ObjectId).primary(),
    id: p.string().serializedPrimaryKey(),
    createdAt: p.datetime().onCreate(() => new Date()),
    updatedAt: p.datetime()
      .onCreate(() => new Date())
      .onUpdate(() => new Date()),
    name: p.string(),
    email: p.string(),
    age: p.integer().nullable(),
    termsAccepted: p.boolean(),
    identities: p.array().nullable(),
    born: p.date().nullable(),
    books: () => p.oneToMany(Book).mappedBy(book => book.author),
    friends: () => p.manyToMany(Author),
    favouriteBook: () => p.manyToOne(Book).nullable(),
    version: p.integer().version(),
  },
});

export class Author extends AuthorSchema.class {}
AuthorSchema.setClass(Author);

More information about modelling relationships can be found on modelling relationships page.

For an example of Vanilla JavaScript usage, take a look here.

Optional Properties​

With the default reflect-metadata provider, you need to mark each optional property as nullable: true. When using ts-morph, if you define the property as optional (marked with ?), this will be automatically considered as nullable property (mainly for SQL schema generator).

./entities/Author.ts
const SomeEntitySchema = defineEntity({
  name: 'SomeEntity',
  properties: {
    favouriteBook: p.manyToOne(Book).nullable(),
  },
});

export class SomeEntity extends SomeEntitySchema.class {}
SomeEntitySchema.setClass(SomeEntity);

To make a nullable field required in methods like em.create() (i.e. you cannot omit the property), use RequiredNullable type. Such property needs to be provided explicitly in the em.create() method, but will accept a null value.

./entities/Book.ts
const BookSchema = defineEntity({
  name: 'Book',
  properties: {
    title: p.string().$type<RequiredNullable<string>>(),
  },
});

em.create(Book, { title: "Alice in Wonderland" }); // ok
em.create(Book, { title: null }); // ok
em.create(Book, {}); // compile error: missing title

Default values​

You can set default value of a property in 2 ways:

  1. Use a property initializer. This approach should be preferred as long as you are not using any native database function like now(). With this approach your entities will have the default value set even before it is actually persisted into the database (e.g. when you instantiate new entity via new Author() or em.create(Author, { ... })).

This is only possible if you have an actual entity class, not an interface. If you use defineEntity without a class, you can use the onCreate option to set the default value.

./entities/Author.ts
const SomeEntitySchema = defineEntity({
  name: 'SomeEntity',
  properties: {
    foo: p.number().onCreate(() => 1),
    bar: p.string().onCreate(() => 'abc'),
    baz: p.datetime().onCreate(() => new Date()),
  },
});

export class SomeEntity extends SomeEntitySchema.class {}
SomeEntitySchema.setClass(SomeEntity);
  1. Use default parameter of @Property decorator. This way the actual default value will be provided by the database, and automatically mapped to the entity property after it is being persisted (after flush). To use SQL functions like now(), use defaultRaw.

Use defaultRaw for SQL functions, as default with string values will be automatically quoted.

./entities/Author.ts
const SomeEntitySchema = defineEntity({
  name: 'SomeEntity',
  properties: {
    foo: p.number().default(1),
    bar: p.string().default('abc'),
    baz: p.datetime().defaultRaw('now'),
  },
});

export class SomeEntity extends SomeEntitySchema.class {}
SomeEntitySchema.setClass(SomeEntity);

Note that the Opt type is used to intersect with the property type to tell the ORM (on type level) that the property should be considered optional for input types (e.g. in em.create()), but will be present for managed entities (e.g. EntityDTO type).

Enums​

To define an enum property, use @Enum() decorator. Enums can be either numeric or string values.

For schema generator to work properly in case of string enums, you need to define the enum in the same file as where it is used, so its values can be automatically discovered. If you want to define the enum in another file, you should re-export it also in place where you use it.

You can also provide the reference to the enum implementation in the decorator via @Enum(() => UserRole).

You can also set enum items manually via items: string[] attribute.

./entities/User.ts
const SomeEntitySchema = defineEntity({
  name: 'SomeEntity',
  properties: {
    // string enum
    role: p.enum(['admin', 'user']),
    // numeric enum
    status: p.enum(() => UserStatus),
    // string enum defined outside of this file
    outside: p.enum(() => OutsideEnum),
    // string enum defined outside of this file, may be null
    outsideNullable: p.enum(() => OutsideNullableEnum).nullable(),
  },
});

export class SomeEntity extends SomeEntitySchema.class {}
SomeEntitySchema.setClass(SomeEntity);

PostgreSQL native enums​

By default, the PostgreSQL driver, represents enums as a text columns with check constraints. Since v6, you can opt in for a native enums by setting the nativeEnumName option.

./entities/User.ts
export enum UserRole {
  ADMIN = 'admin',
  MODERATOR = 'moderator',
  USER = 'user',
}

const SomeEntitySchema = defineEntity({
  name: 'SomeEntity',
  properties: {
    role: p.enum(() => UserRole).nativeEnumName('user_role'),
  },
});

export class SomeEntity extends SomeEntitySchema.class {}
SomeEntitySchema.setClass(SomeEntity);

Enum arrays​

You can also use array of values for enum, in that case, EnumArrayType type will be used automatically, that will validate items on flush.

./entities/User.ts
enum Role {
  User = 'user',
  Admin = 'admin',
}

const SomeEntitySchema = defineEntity({
  name: 'SomeEntity',
  properties: {
    roles: p.enum(() => Role).array().default([Role.User]),
  },
});

export class SomeEntity extends SomeEntitySchema.class {}
SomeEntitySchema.setClass(SomeEntity);

Mapping directly to primary keys​

Sometimes you might want to work only with the primary key of a relation. To do that, you can use mapToPk option on M:1 and 1:1 relations:

./entities/User.ts
const SomeEntitySchema = defineEntity({
  name: 'SomeEntity',
  properties: {
    user: () => p.manyToOne(User).mapToPk(),
  },
});

export class SomeEntity extends SomeEntitySchema.class {}
SomeEntitySchema.setClass(SomeEntity);

For composite keys, this will give us ordered tuple representing the raw PKs, which is the internal format of composite PK:

./entities/User.ts
const SomeEntitySchema = defineEntity({
  name: 'SomeEntity',
  properties: {
    user: () => p.manyToOne(User).mapToPk(),
  },
});

export class SomeEntity extends SomeEntitySchema.class {}
SomeEntitySchema.setClass(SomeEntity);

Formulas​

@Formula() decorator can be used to map some SQL snippet to your entity. The SQL fragment can be as complex as you want and even include subselects.

./entities/Box.ts
const BoxSchema = defineEntity({
  name: 'Box',
  properties: {
    objectVolume: p.formula<number>('obj_length * obj_height * obj_width'),
  },
});

export class Box extends BoxSchema.class {}
BoxSchema.setClass(Box);

Formulas will be added to the select clause automatically. You can define the formula as a callback that receives a columns object mapping property names to their unquoted column references (e.g., alias.field_name). Use the quote helper for proper identifier quoting across all database platforms:

./entities/Box.ts
import { quote } from '@mikro-orm/core';

const BoxSchema = defineEntity({
  name: 'Box',
  properties: {
    objectVolume: p.formula<number>(cols => quote`${cols.objLength} * ${cols.objHeight} * ${cols.objWidth}`),
  },
});

export class Box extends BoxSchema.class {}
BoxSchema.setClass(Box);

The columns object:

  • Maps property names to fully-qualified alias.field_name references
  • Works correctly with TPT (Table-Per-Type) inheritance - inherited properties automatically use the parent table's alias
  • Has toString() returning the table alias for backwards compatibility

For more complex scenarios, you can use an enhanced callback signature that provides access to table metadata:

@Formula((cols, table) => {
  return `(select count(*) from other_table where other_table.ref_id = ${table.qualifiedName}.${cols.id})`;
})
relatedCount?: number;

The table parameter provides:

  • alias: The quoted table alias
  • name: The table name
  • schema: The schema name (if applicable)
  • qualifiedName: The schema-qualified table name (schema.table or just table)
  • toString(): Returns the alias for convenience in template literals

Indexes​

You can define indexes via @Index() decorator, for unique indexes, you can use @Unique() decorator. You can use it either on entity class, or on entity property.

Comprehensive Index Guide

For advanced index features including column sort order, NULLS ordering, prefix length, covering indexes (INCLUDE), fill factor, invisible indexes, clustered indexes, and database-specific options, see the dedicated Indexes and Unique Constraints guide.

To define complex indexes, you can use index expressions. They allow you to specify the final create index query and an index name - this name is then used for index diffing, so the schema generator will only try to create it if it's not there yet, or remove it, if it's no longer defined in the entity. Index expressions are not bound to any property, rather to the entity itself (you can still define them on both entity and property level).

To define an index expression, you can either provide a raw SQL string, or use the expression callback to dynamically build the returned SQL.

./entities/Author.ts
const AuthorSchema = defineEntity({
  name: 'Author',
  properties: {
    email: p.string().unique(),
    age: p.number().nullable().index(),
    born: p.date().nullable().index('born_index'),
    title: p.string(),
    country: p.string(),
  },
  indexes: [
    { properties: ['name', 'age'] }, // compound index, with generated name
    { name: 'custom_idx_name', properties: ['name'] }, // simple index, with custom name
    // Custom index using expression callback
    // ${table.schema}, ${table.name}, and ${columns.title} return the unquoted identifiers.
    { name: 'custom_index_country1', expression: (columns, table, indexName) => `create index \`${indexName}\` on \`${table.schema}\`.\`${table.name}\` (\`${columns.country}\`)` },
    // Using quote helper to automatically quote identifiers.
    { name: 'custom_index_country2', expression: (columns, table, indexName) => quote`create index ${indexName} on ${table} (${columns.country})` },
    // Using raw function to automatically quote identifiers.
    { name: 'custom_index_country3', expression: (columns, table, indexName) => raw(`create index ?? on ?? (??)`, [indexName, table, columns.country]) },
  ],
  uniques: [
    { properties: ['name', 'email'] },
  ],
});

export class Author extends AuthorSchema.class {}
AuthorSchema.setClass(Author);

Check constraints​

You can define check constraints via @Check() decorator. You can use it either on entity class, or on entity property. It has a required expression property, that can be either a string or a callback, that receives map of property names to column names. Note that you need to use the generic type argument if you want TypeScript suggestions for the property names.

Check constraints are currently supported only in postgres driver.

./entities/Book.ts
const BookSchema = defineEntity({
  name: 'Book',
  properties: {
    id: p.number().primary(),
    price1: p.number(),
    price2: p.number(),
    price3: p.number(),
  },
  checks: [
    { expression: 'price1 >= 0' },
    { name: 'foo', expression: columns => `${columns.price1} >= 0` },
    { expression: columns => `${columns.price1} >= 0` },
    { propertyName: 'price2', expression: 'price2 >= 0' },
    { propertyName: 'price3', expression: columns => `${columns.price3} >= 0` },
  ],
});

export class Book extends BookSchema.class {}
BookSchema.setClass(Book);

Custom Types​

You can define custom types by extending Type abstract class. It has 4 optional methods:

  • convertToDatabaseValue(value: any, platform: Platform): any

    Converts a value from its JS representation to its database representation of this type.

  • convertToJSValue(value: any, platform: Platform): any

    Converts a value from its database representation to its JS representation of this type.

  • toJSON(value: any, platform: Platform): any

    Converts a value from its JS representation to its serialized JSON form of this type. By default, converts to the database value.

  • getColumnType(prop: EntityProperty, platform: Platform): string

    Gets the SQL declaration snippet for a field of this type.

More information can be found in Custom Types section.

Lazy scalar properties​

You can mark any property as lazy: true to omit it from the select clause. This can be handy for properties that are too large, and you want to have them available only sometimes, like a full text of an article.

./entities/Book.ts
const BookSchema = defineEntity({
  name: 'Book',
  properties: {
    text: p.text().lazy(),
  },
});

export class Book extends BookSchema.class {}
BookSchema.setClass(Book);

You can use populate parameter to load them.

const b1 = await em.find(Book, 1); // this will omit the `text` property
const b2 = await em.find(Book, 1, { populate: ['text'] }); // this will load the `text` property

If the entity is already loaded, and you need to populate a lazy scalar property, you might need to pass refresh: true in the FindOptions.

ScalarReference wrapper​

Similarly to the Reference wrapper, you can also wrap lazy scalars with Ref into a ScalarReference object. The Ref type automatically resolves to ScalarReference for non-object types, so the below is correct:

@Property({ lazy: true, ref: true })
passwordHash!: Ref<string>;
const user = await em.findOne(User, 1);
const passwordHash = await user.passwordHash.load();

For object-like types, if you choose to use the reference wrappers, you should use the ScalarRef<T> type explicitly. For example, you might want to lazily load a large JSON value:

@Property({ type: 'json', nullable: true, lazy: true, ref: true })
// ReportParameters is an object type, imagine it defined elsewhere.
reportParameters!: ScalarRef<ReportParameters | null>;

Keep in mind that once a scalar value is managed through a ScalarReference, accessing it through MikroORM managed objects will always return the ScalarReference wrapper. That can be confusing in case the property is also nullable, since the ScalarReference will always be truthy. In such cases, you should inform the type system of the nullability of the property through ScalarReference<T>'s type parameter as demonstrated above. Below is an example of how it all works:

// Say Report of id "1" has no reportParameters in the Database.
const report = await em.findOne(Report, 1);
if (report.reportParameters) {
  // Logs Ref<?>, not the actual value. **Would always run***.
  console.log(report.reportParameters);
  //@ts-expect-error $/.get() is not available until the reference has been loaded.
  // const mistake = report.reportParameters.$
}
const populatedReport = await em.populate(report, ['reportParameters']);
// Logs `null`
console.log(populatedReport.reportParameters.$);

Private property accessors​

When using a private property backed by a public get/set pair, use the accessor option to point to the other side.

The fieldName will be inferred based on the accessor name unless specified explicitly.

If the accessor option points to something, the ORM will use the backing property directly:

./entities/User.ts
export class User {
  id!: number;
  private _email!: unknown;

  get email(): unknown {
    return this._email;
  }

  set email(email: unknown) {
    this._email = email;
  }
}

export const UserSchema = defineEntity({
  class: User,
  properties: {
    id: p.integer().primary(),
    // the ORM will use the backing field directly
    email: p.string().accessor('_email'),
  },
});

If you want the ORM to use the accessor internally (e.g. for hydration or change tracking), use accessor: true on the get/set property instead. This is handy if you want to use a native private property for the backing field.

./entities/User.ts
export class User {
  id!: string;
  #email!: string;

  get email() {
    return this.#email;
  }

  set email(email: string) {
    return this.#email;
  }
}

export const UserSchema = defineEntity({
  class: User,
  // constructors are required for native private fields
  forceConstructor: true,
  properties: {
    id: p.integer().primary(),
    // the ORM will use the accessor internally
    email: p.string().accessor(),
  },
});

Virtual Properties​

You can define your properties as virtual, either as a method, or via JavaScript get/set.

Following example defines User entity with firstName and lastName database fields, that are both hidden from the serialized response, replaced with virtual properties fullName (defined as a classic method) and fullName2 (defined as a JavaScript getter).

For JavaScript getter you need to provide { persist: false } option otherwise the value would be stored in the database.

./entities/User.ts
export class User {

  [HiddenProps]?: 'firstName' | 'lastName';

  firstName!: string;
  lastName!: string;

  getFullName() {
    return `${this.firstName} ${this.lastName}`;
  }

  get fullName2() {
    return `${this.firstName} ${this.lastName}`;
  }
}

export const UserSchema = defineEntity({
  class: User,
  name: 'User',
  properties: {
    firstName: p.string().hidden(),
    lastName: p.string().hidden(),
    fullName: p.type('method').persist(false).getter().getterName('getFullName'),
    fullName2: p.type('method').persist(false).getter(),
  },
});
const repo = em.getRepository(User);
const author = repo.create({ firstName: 'Jon', lastName: 'Snow' });

console.log(author.getFullName()); // 'Jon Snow'
console.log(author.fullName2); // 'Jon Snow'
console.log(wrap(author).toJSON()); // { fullName: 'Jon Snow', fullName2: 'Jon Snow' }

Entity file names​

Starting with MikroORM 4.2, there is no limitation for entity file names. It is now also possible to define multiple entities in a single file using folder based discovery.

Default entity ordering​

You can define a default ordering for an entity using the orderBy option in @Entity(). This ordering is automatically applied when:

  • Querying the entity directly via em.find(), em.findAll(), etc.
  • Populating the entity as a relation

All applicable orderings are combined together, with higher-priority orderings taking precedence for the same fields.

./entities/Comment.ts
import { defineEntity, p } from '@mikro-orm/core';

const CommentSchema = defineEntity({
  name: 'Comment',
  orderBy: { createdAt: QueryOrder.DESC, id: QueryOrder.DESC },
  properties: {
    id: p.number().primary(),
    createdAt: p.datetime(),
    text: p.string(),
    post: () => p.manyToOne(Post),
  },
});

export class Comment extends CommentSchema.class {}
CommentSchema.setClass(Comment);

The ordering precedence (from highest to lowest) is:

  1. Runtime orderBy - Passed to em.find(), collection.init(), or collection.matching()
  2. Relation-level orderBy - Defined on @OneToMany() or @ManyToMany() decorators
  3. Entity-level orderBy - Defined on the @Entity() decorator

All levels are combined together - if you specify { name: 'asc' } at runtime and the entity has { createdAt: 'desc' }, the result will order by name first, then by createdAt.

./entities/Post.ts
import { defineEntity, p } from '@mikro-orm/core';

const PostSchema = defineEntity({
  name: 'Post',
  properties: {
    id: p.number().primary(),
    comments: () => p.oneToMany(Comment).mappedBy('post'),
    commentsAlphabetical: () => p.oneToMany(Comment).mappedBy('post').orderBy({ text: QueryOrder.ASC }),
  },
});

export class Post extends PostSchema.class {}
PostSchema.setClass(Post);
const comments = await em.find(Comment, {});
// ordered by createdAt DESC (entity-level), then by id DESC

const commentsAsc = await em.find(Comment, {}, { orderBy: { createdAt: QueryOrder.ASC } });
// ordered by createdAt ASC (runtime), then by id DESC (entity-level)

const post = await em.findOne(Post, 1, { populate: ['comments'] });
// post.comments ordered by createdAt DESC, id DESC

Using custom base entity​

You can define your own base entity with properties that are required on all entities, like primary key and created/updated time. MikroORM supports two inheritance mapping strategies:

  • Single Table Inheritance (STI) - All entities in the hierarchy share a single table with a discriminator column
  • Table-Per-Type Inheritance (TPT) - Each entity has its own table with foreign keys linking child tables to parent tables

Read more about this topic in Inheritance Mapping section.

If you are initializing the ORM via entities option, you need to specify all your base entities as well.

./entities/CustomBaseEntity.ts
const p = defineEntity.properties;
const CustomBaseProperties = {
  uuid: p.uuid().primary().onCreate(() => v4()),
  createdAt: p.datetime()
    .onCreate(() => new Date())
    .nullable(),
  updatedAt: p.datetime()
    .onCreate(() => new Date())
    .onUpdate(() => new Date())
    .nullable(),
}

There is a special case, when you need to annotate the base entity - if you are using folder based discovery, and the base entity is not using any decorators (e.g. it does not define any decorated property). In that case, you need to mark it as abstract:

@Entity({ abstract: true })
export abstract class CustomBaseEntity {
  // ...
}

SQL Generated columns​

To use generated columns, you can either use the generated option, or specify it as part of the columnType:

./entities/User.ts
const UserSchema = defineEntity({
  name: 'User',
  properties: {
    id: p.integer().primary(),
    firstName: p.string().length(50),
    lastName: p.string().length(50),
    fullName: p.string()
      .length(100)
      .generated(cols => `(concat(${cols.firstName}, ' ', ${cols.lastName})) stored`),
    fullName2: p.string()
      .length(100)
      .columnType(`varchar(100) generated always as (concat(first_name, ' ', last_name)) virtual`),
  },
});

export class User extends UserSchema.class {}
UserSchema.setClass(User);

To use a generated identity column in PostgreSQL, set the generated option to identity:

To allow providing the value explicitly, use generated: 'by default as identity'.

./entities/User.ts
const UserSchema = defineEntity({
  name: 'User',
  properties: {
    id: p.integer().primary().generated('identity'),
  },
});

export class User extends UserSchema.class {}
UserSchema.setClass(User);

Examples of entity definition with various primary keys​

Using id as primary key (SQL drivers)​

./entities/Book.ts
const BookSchema = defineEntity({
  name: 'Book',
  properties: {
    id: p.integer().primary(),
    title: p.string(),
    author: () => p.manyToOne(Author),
    publisher: () => p.manyToOne(Publisher).nullable(),
  },
});

export class Book extends BookSchema.class {}
BookSchema.setClass(Book);

Using UUID as primary key (SQL drivers)​

./entities/Book.ts
const BookSchema = defineEntity({
  name: 'Book',
  properties: {
    uuid: p.uuid().primary().onCreate(() => v4()),
    title: p.string(),
    author: () => p.manyToOne(Author),
  },
});

export class Book extends BookSchema.class {}
BookSchema.setClass(Book);

Using PostgreSQL built-in gen_random_uuid function as primary key​

./entities/Book.ts
const BookSchema = defineEntity({
  name: 'Book',
  properties: {
    uuid: p.uuid().primary().defaultRaw('gen_random_uuid()'),
    title: p.string(),
    author: () => p.manyToOne(Author),
  },
});

export class Book extends BookSchema.class {}
BookSchema.setClass(Book);

Using BigInt as primary key (MySQL and PostgreSQL)​

Since v6, bigints are represented by the native BigInt type, and as such, they don't require explicit type in the decorator options:

@PrimaryKey()
id: bigint;

You can also specify the target type you want your bigints to be mapped to:

@PrimaryKey({ type: new BigIntType('bigint') })
id1: bigint;

@PrimaryKey({ type: new BigIntType('string') })
id2: string;

@PrimaryKey({ type: new BigIntType('number') })
id3: number;

JavaScript cannot represent all the possible values of a bigint when mapping to the number type - only values up to Number.MAX_SAFE_INTEGER (2^53 - 1) are safely supported.

./entities/CustomBaseEntity.ts
const SomeEntitySchema = defineEntity({
  name: 'SomeEntity',
  properties: {
    id: p.bigint().primary(),
  },
});

export class SomeEntity extends SomeEntitySchema.class {}
SomeEntitySchema.setClass(SomeEntity);

If you want to use native bigints, read the following guide: Using native BigInt PKs.

Example of Mongo entity​

./entities/Book.ts
const BookSchema = defineEntity({
  name: 'Book',
  properties: {
    _id: p.type(ObjectId).primary(),
    id: p.string().serializedPrimaryKey(),
    title: p.string(),
  },
});

export class Book extends BookSchema.class {}
BookSchema.setClass(Book);

Using MikroORM's BaseEntity (previously WrappedEntity)​

The BaseEntity class is provided with init, isInitialized, assign and other methods that are otherwise available via the wrap() helper.

Usage of the BaseEntity is optional.

import { BaseEntity } from '@mikro-orm/core';

@Entity()
export class Book extends BaseEntity {

  @PrimaryKey()
  id!: number;

  @Property()
  title!: string;

  @ManyToOne()
  author!: Author;

}

const book = new Book();
console.log(book.isInitialized()); // true

Having the entities set up, you can now start using entity manager and repositories as described in following sections.