TypeORM 中文文档

# 更新日志-未翻译

# 0.3.7 (opens new window) (2022-06-29)

# Bug Fixes

# Features

# Performance Improvements

# 0.3.6 (opens new window) (2022-04-12)

# Features

# 0.3.5 (opens new window) (2022-04-05)

# Bug Fixes

# 0.3.4 (opens new window) (2022-03-26)

# Bug Fixes

# Features

# 0.3.3 (opens new window) (2022-03-23)

# Bug Fixes

# Features

# 0.3.2 (opens new window) (2022-03-22)

# Bug Fixes

# Features

# Reverts

# 0.3.1 (opens new window) (2022-03-21)

# Bug Fixes

# Features

# BREAKING CHANGES

  • we do not call JSON.stringify() to json/jsonb column types in Postgres. Instead, we delegate value directly to underlying pg driver. This is a correct way of handling jsons.
  • array: true must be explicitly defined for array json/jsonb values
  • strings being JSON-stringified must be manually escaped

# 0.3.0 (opens new window) (2022-03-17)

Changes in the version includes changes from the next branch and typeorm@next version. They were pending their migration from 2018. Finally, they are in the master branch and master version.

# Features

  • compilation target now is es2020. This requires Node.JS version 14+

  • TypeORM now properly works when installed within different node_modules contexts (often happen if TypeORM is a dependency of another library or TypeORM is heavily used in monorepo projects)

  • Connection was renamed to DataSource. Old Connection is still there, but now it's deprecated. It will be completely removed in next version. New API:

export const dataSource = new DataSource({
    // ... options ...
})

// load entities, establish db connection, sync schema, etc.
await dataSource.connect()
1
2
3
4
5
6

Previously, you could use new Connection(), createConnection(), getConnectionManager().create(), etc. They all deprecated in favour of new syntax you can see above.

New way gives you more flexibility and simplicity in usage.

  • new custom repositories syntax:
export const UserRepository = myDataSource.getRepository(UserEntity).extend({
    findUsersWithPhotos() {
        return this.find({
            relations: {
                photos: true
            }
        })
    }
})
1
2
3
4
5
6
7
8
9

Old ways of custom repository creation were dropped.

  • added new option on relation load strategy called relationLoadStrategy. Relation load strategy is used on entity load and determines how relations must be loaded when you query entities and their relations from the database. Used on find* methods and QueryBuilder. Value can be set to join or query.

    • join - loads relations using SQL JOIN expression
    • query - executes separate SQL queries for each relation

Default is join, but default can be set in ConnectionOptions:

createConnection({
    /* ... */
    relationLoadStrategy: "query"
})
1
2
3
4

Also, it can be set per-query in find* methods:

userRepository.find({
    relations: {
        photos: true
    }
})
1
2
3
4
5

And QueryBuilder:

userRepository
    .createQueryBuilder()
    .setRelationLoadStrategy("query")
1
2
3

For queries returning big amount of data, we recommend to use query strategy, because it can be a more performant approach to query relations.

  • added new findOneBy, findOneByOrFail, findBy, countBy, findAndCountBy methods to BaseEntity, EntityManager and Repository:
const users = await userRepository.findBy({
    name: "Michael"
})
1
2
3

Overall find* and count* method signatures where changed, read the "breaking changes" section for more info.

  • new select type signature in FindOptions (used in find* methods):
userRepository.find({
    select: {
        id: true,
        firstName: true,
        lastName: true,
    }
})
1
2
3
4
5
6
7

Also, now it's possible to specify select columns of the loaded relations:

userRepository.find({
    select: {
        id: true,
        firstName: true,
        lastName: true,
        photo: {
            id: true,
            filename: true,
            album: {
                id: true,
                name: true,
            }
        }
    }
})
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
  • new relations type signature in FindOptions (used in find* methods):
userRepository.find({
    relations: {
        contacts: true,
        photos: true,
    }
})
1
2
3
4
5
6

To load nested relations use a following signature:

userRepository.find({
    relations: {
        contacts: true,
        photos: {
            album: true,
        },
    }
})
1
2
3
4
5
6
7
8
  • new order type signature in FindOptions (used in find* methods):
userRepository.find({
    order: {
        id: "ASC"
    }
})
1
2
3
4
5

Now supports nested order by-s:

userRepository.find({
    order: {
        photos: {
            album: {
                name: "ASC"
            },
        },
    }
})
1
2
3
4
5
6
7
8
9
  • new where type signature in FindOptions (used in find* methods) now allows to build nested statements with conditional relations, for example:
userRepository.find({
    where: {
        photos: {
            album: {
                name: "profile"
            }
        }
    }
})
1
2
3
4
5
6
7
8
9

Gives you users who have photos in their "profile" album.

  • FindOperator-s can be applied for relations in where statement, for example:
userRepository.find({
    where: {
        photos: MoreThan(10),
    }
})
1
2
3
4
5

Gives you users with more than 10 photos.

  • boolean can be applied for relations in where statement, for example:
userRepository.find({
    where: {
        photos: true
    }
})
1
2
3
4
5

# BREAKING CHANGES

  • minimal Node.JS version requirement now is 14+

  • drop ormconfig support. ormconfig still works if you use deprecated methods, however we do not recommend using it anymore, because it's support will be completely dropped in 0.4.0. If you want to have your connection options defined in a separate file, you can still do it like this:

import ormconfig from "./ormconfig.json"

const MyDataSource = new DataSource(require("./ormconfig.json"))
1
2
3

Or even more type-safe approach with resolveJsonModule in tsconfig.json enabled:

import ormconfig from "./ormconfig.json"

const MyDataSource = new DataSource(ormconfig)
1
2
3

But we do not recommend use this practice, because from 0.4.0 you'll only be able to specify entities / subscribers / migrations using direct references to entity classes / schemas (see "deprecations" section).

We won't be supporting all ormconfig extensions (e.g. json, js, ts, yaml, xml, env).

  • support for previously deprecated migrations:* commands was removed. Use migration:* commands instead.

  • all commands were re-worked. Please refer to new CLI documentation.

  • cli option from BaseConnectionOptions (now BaseDataSourceOptions options) was removed (since CLI commands were re-worked).

  • now migrations are running before schema synchronization if you have both pending migrations and schema synchronization pending (it works if you have both migrationsRun and synchronize enabled in connection options).

  • aurora-data-api driver now is called aurora-mysql

  • aurora-data-api-pg driver now is called aurora-postgres

  • EntityManager.connection is now EntityManager.dataSource

  • Repository now has a constructor (breaks classes extending Repository with custom constructor)

  • @TransactionRepository, @TransactionManager, @Transaction decorators were completely removed. These decorators do the things out of the TypeORM scope.

  • Only junction table names shortened.

MOTIVATION: We must shorten only table names generated by TypeORM. It's user responsibility to name tables short if their RDBMS limit table name length since it won't make sense to have table names as random hashes. It's really better if user specify custom table name into @Entity decorator. Also, for junction table it's possible to set a custom name using @JoinTable decorator.

  • findOne() signature without parameters was dropped. If you need a single row from the db you can use a following syntax:
const [user] = await userRepository.find()
1

This change was made to prevent user confusion. See this issue (opens new window) for details.

  • findOne(id) signature was dropped. Use following syntax instead:
const user = await userRepository.findOneBy({
    id: id // where id is your column name
})
1
2
3

This change was made to provide a more type-safe approach for data querying. Due to this change you might need to refactor the way you load entities using MongoDB driver.

  • findOne, findOneOrFail, find, count, findAndCount methods now only accept FindOptions as parameter, e.g.:
const users = await userRepository.find({
    where: { /* conditions */ },
    relations: { /* relations */ }
})
1
2
3
4

To supply where conditions directly without FindOptions new methods were added: findOneBy, findOneByOrFail, findBy, countBy, findAndCountBy. Example:

const users = await userRepository.findBy({
    name: "Michael"
})
1
2
3

This change was required to simply current find* and count* methods typings, improve type safety and prevent user confusion.

  • findByIds was deprecated, use findBy method instead in conjunction with In operator, for example:
userRepository.findBy({
    id: In([1, 2, 3])
})
1
2
3

This change was made to provide a more type-safe approach for data querying.

  • findOne and QueryBuilder.getOne() now return null instead of undefined in the case if it didn't find anything in the database. Logically it makes more sense to return null.

  • findOne now limits returning rows to 1 at database level.

NOTE: FOR UPDATE locking does not work with findOne in Oracle since FOR UPDATE cannot be used with FETCH NEXT in a single query.

  • where in FindOptions (e.g. find({ where: { ... })) is more sensitive to input criteria now.

  • FindConditions (where in FindOptions) was renamed to FindOptionsWhere.

  • null as value in where used in find* methods is not supported anymore. Now you must explicitly use IsNull() operator.

Before:

userRepository.find({
    where: {
        photo: null
    }
})
1
2
3
4
5

After:

userRepository.find({
    where: {
        photo: IsNull()
    }
})
1
2
3
4
5

This change was made to make it more transparent on how to add "IS NULL" statement to final SQL, because before it bring too much confusion for ORM users.

  • if you had entity properties of a non-primitive type (except Buffer) defined as columns, then you won't be able to use it in find*'s where. Example:

Before for the @Column(/*...*/) membership: MembershipKind you could have a query like:

userRepository.find({
    membership: new MembershipKind("premium")
})
1
2
3

now, you need to wrap this value into Equal operator:

userRepository.find({
    membership: Equal(new MembershipKind("premium"))
})
1
2
3

This change is due to type-safety improvement new where signature brings.

  • order in FindOptions (used in find* methods) doesn't support ordering by relations anymore. Define relation columns, and order by them instead.

  • where in FindOptions (used in find* methods) previously supported ObjectLiteral and string types. Now both signatures were removed. ObjectLiteral was removed because it seriously breaks the type safety, and string doesn't make sense in the context of FindOptions. Use QueryBuilder instead.

  • MongoRepository and MongoEntityManager now use new types called MongoFindManyOptions and MongoFindOneOptions for their find* methods.

  • primary relation (e.g. @ManyToOne(() => User, { primary: true }) user: User) support is removed. You still have an ability to use foreign keys as your primary keys, however now you must explicitly define a column marked as primary.

Example, before:

@ManyToOne(() => User, { primary: true })
user: User
1
2

Now:

@PrimaryColumn()
userId: number

@ManyToOne(() => User)
user: User
1
2
3
4
5

Primary column name must match the relation name + join column name on related entity. If related entity has multiple primary keys, and you want to point to multiple primary keys, you can define multiple primary columns the same way:

@PrimaryColumn()
userFirstName: string

@PrimaryColumn()
userLastName: string

@ManyToOne(() => User)
user: User
1
2
3
4
5
6
7
8

This change was required to simplify ORM internals and introduce new features.

# DEPRECATIONS

  • all CLI commands do not support ormconfig anymore. You must specify a file with data source instance instead.

  • entities, migrations, subscribers options inside DataSourceOptions accepting string directories support is deprecated. You'll be only able to pass entity references in the future versions.

  • all container-related features (UseContainerOptions, ContainedType, ContainerInterface, defaultContainer, useContainer, getFromContainer) are deprecated.

  • EntityManager's getCustomRepository used within transactions is deprecated. Use withRepository method instead.

  • Connection.isConnected is deprecated. Use .isInitialized instead.

  • select in FindOptions (used in find* methods) used as an array of property names is deprecated. Now you should use a new object-literal notation. Example:

Deprecated way of loading entity relations:

userRepository.find({
    select: ["id", "firstName", "lastName"]
})
1
2
3

New way of loading entity relations:

userRepository.find({
    select: {
        id: true,
        firstName: true,
        lastName: true,
    }
})
1
2
3
4
5
6
7

This change is due to type-safety improvement new select signature brings.

  • relations in FindOptions (used in find* methods) used as an array of relation names is deprecated. Now you should use a new object-literal notation. Example:

Deprecated way of loading entity relations:

userRepository.find({
    relations: ["contacts", "photos", "photos.album"]
})
1
2
3

New way of loading entity relations:

userRepository.find({
    relations: {
        contacts: true,
        photos: {
            album: true
        }
    }
})
1
2
3
4
5
6
7
8

This change is due to type-safety improvement new relations signature brings.

  • join in FindOptions (used in find* methods) is deprecated. Use QueryBuilder to build queries containing manual joins.

  • Connection, ConnectionOptions are deprecated, new names to use are: DataSource and DataSourceOptions. To create the same connection you had before use a new syntax: new DataSource({ /*...*/ }).

  • createConnection(), createConnections() are deprecated, since Connection is called DataSource now, to create a connection and connect to the database simply do:

const myDataSource = new DataSource({ /*...*/ })
await myDataSource.connect()
1
2
  • getConnection() is deprecated. To have a globally accessible connection, simply export your data source and use it in places you need it:
export const myDataSource = new DataSource({ /*...*/ })
// now you can use myDataSource anywhere in your application
1
2
  • getManager(), getMongoManager(), getSqljsManager(), getRepository(), getTreeRepository(), getMongoRepository(), createQueryBuilder() are all deprecated now. Use globally accessible data source instead:
export const myDataSource = new DataSource({ /*...*/ })
export const Manager = myDataSource.manager
export const UserRepository = myDataSource.getRepository(UserEntity)
export const PhotoRepository = myDataSource.getRepository(PhotoEntity)
// ...
1
2
3
4
5
  • getConnectionManager() and ConnectionManager itself are deprecated - now Connection is called DataSource, and each data source can be defined in exported variable. If you want to have a collection of data sources, just define them in a variable, simply as:
const dataSource1 = new DataSource({ /*...*/ })
const dataSource2 = new DataSource({ /*...*/ })
const dataSource3 = new DataSource({ /*...*/ })

export const MyDataSources = {
    dataSource1,
    dataSource2,
    dataSource3,
}
1
2
3
4
5
6
7
8
9

  • getConnectionOptions() is deprecated - in next version we are going to implement different mechanism of connection options loading

  • AbstractRepository is deprecated. Use new way of custom repositories creation.

  • Connection.name and BaseConnectionOptions.name are deprecated. Connections don't need names anymore since we are going to drop all related methods relying on this property.

  • all deprecated signatures will be removed in 0.4.0

# EXPERIMENTAL FEATURES NOT PORTED FROM NEXT BRANCH

  • observers - we will consider returning them back with new API in future versions
  • alternative find operators - using $any, $in, $like and other operators in where condition.

# 0.2.45 (opens new window) (2022-03-04)

# Bug Fixes

# Features

# 0.2.44 (opens new window) (2022-02-23)

# Bug Fixes

# Features

# 0.2.43 (opens new window) (2022-02-17)

# Bug Fixes

# Features

# Reverts

# 0.2.42 (opens new window) (2022-02-16)

# Bug Fixes

# Features

# Reverts

# BREAKING CHANGES

  • update listeners and subscriber no longer triggered by soft-remove and recover

# 0.2.41 (opens new window) (2021-11-18)

# Bug Fixes

# Features

# 0.2.40 (opens new window) (2021-11-11)

# Bug Fixes

# Features

# Reverts

# 0.2.39 (opens new window) (2021-11-09)

# Bug Fixes

# Features

# Reverts

# 0.2.38 (opens new window) (2021-10-02)

# Bug Fixes

# Features

# 0.2.37 (opens new window) (2021-08-13)

# Bug Fixes

# Features

# 0.2.36 (opens new window) (2021-07-31)

# Bug Fixes

# Features

# 0.2.35 (opens new window) (2021-07-28)

# Bug Fixes

# Features

# 0.2.34 (opens new window) (2021-06-03)

# Bug Fixes

# 0.2.33 (opens new window) (2021-06-01)

# Bug Fixes

# Features

# 0.2.32 (opens new window) (2021-03-30)

# Bug Fixes

# Features

# 0.2.31 (opens new window) (2021-02-08)

# Bug Fixes

# Features

# BREAKING CHANGES

  • passing ColumnOptions to @PrimaryColumn does not function anymore. One must use PrimaryColumnOptions instead.
  • minor breaking change on "conflict*" options - column names used are now automatically escaped.

# 0.2.30 (opens new window) (2021-01-12)

# Bug Fixes

# Features

# 0.2.29 (opens new window) (2020-11-02)

# Bug Fixes

# Features

# Performance Improvements

# 0.2.28 (opens new window) (2020-09-30)

# Bug Fixes

# 0.2.27 (opens new window) (2020-09-29)

# Bug Fixes

# Features

# Reverts

# 0.2.26 (opens new window) (2020-09-10)

# Bug Fixes

# Features

# 0.2.25 (opens new window) (2020-05-19)

# Bug Fixes

# Features

# Performance Improvements

# 0.2.23 (opens new window), 0.2.24 (opens new window) (2020-02-28)

# Bug Fixes

# Features

# 0.2.22 (opens new window) (2019-12-23)

# Bug Fixes

# Features

# BREAKING CHANGES

  • aliases for very long relation names may be replaced with hashed strings. Fix: avoid collisions by using longest possible hash. Retain more entropy by not using only 8 characters of hashed aliases.

# 0.2.21 (opens new window) (2019-12-05)

# Bug Fixes

# Features

# 0.2.20 (opens new window) (2019-10-18)

# Bug Fixes

# Features

# 0.2.19 (opens new window) (2019-09-13)

# Bug Fixes

# Features

# 0.2.18

# Bug fixes

# Features

# 0.2.17 (2019-05-01)

# Bug fixes

# Features

# 0.2.16 (2019-03-26)

# Bug fixes