All Versions
89
Latest Version
Avg Release Cycle
24 days
Latest Release
481 days ago

Changelog History
Page 6

  • v0.2.7 Changes

    • โž• added support for rowversion type for mssql (#2198)
  • v0.2.6 Changes

    • ๐Ÿ›  fixed wrong aggregate and count methods signature in mongodb
  • v0.2.5 Changes

    • โž• added support for enum arrays in postgres
    • ๐Ÿ›  fixed issue with lazy relations (#1953)
    • ๐Ÿ›  fixed issue with migration file generator using a wrong class name (#2070)
    • ๐Ÿ›  fixed issue with unhandled promise rejection warning on postgres connection (#2067)
  • v0.2.4 Changes

    • ๐Ÿ›  fixed bug with relation id loader queries not working with self-referencing relations
    • ๐Ÿ›  fixed issues with zerofill and unsigned options not available in column options (#2049)
    • ๐Ÿ›  fixed issue with lazy relation loader (#2029)
    • ๐Ÿ›  fixed issue with closure table not properly escaped when using custom schema (#2043)
    • ๐Ÿ›  fixed issue #2053
  • v0.2.3 Changes

    • ๐Ÿ›  fixed bug with selecting default values after persistence when initialized properties defined
    • ๐Ÿ›  fixed bug with find operators used on relational columns (#2031)
    • ๐Ÿ›  fixed bug with DEFAULT as functions in mssql (#1991)
  • v0.2.2 Changes

    • ๐Ÿ›  fixing bugs with STI
    • ๐Ÿ›  fixed bug in mysql schema synchronization
  • v0.2.1 Changes

    • ๐Ÿ›  fixed bug with STI
    • ๐Ÿ›  fixed bug with lazy relations inside transactions
  • v0.2.0 Changes

    • ๐ŸŽ completely refactored, improved and optimized persistence process and performance.
    • โœ‚ removed cascade remove functionality, refactored how cascades are working.
    • โœ‚ removed cascadeRemove option from relation options.
    • replaced cascadeAll with cascade: true syntax from relation options.
    • replaced cascadeInsert with cascade: ["insert"] syntax from relation options.
    • โšก๏ธ replaced cascadeUpdate with cascade: ["update"] syntax from relation options.
    • now when one-to-one or many-to-one relation is loaded and its not set (set to null) ORM returns you entity with relation set to null instead of undefined property as before.
    • now relation id can be set directly to relation, e.g. Post { @ManyToOne(type => Tag) tag: Tag|number } with post.tag = 1 usage.
    • ๐ŸŽ now you can disable persistence on any relation by setting @OneToMany(type => Post, post => tag, { persistence: false }). This can dramatically improve entity save performance.
    • 0๏ธโƒฃ loadAllRelationIds method of QueryBuilder now accepts list of relation paths that needs to be loaded, also disableMixedMap option is now by default set to false, but you can enable it via new method parameter options
    • ๐Ÿ‘ now returning and output statements of InsertQueryBuilder support array of columns as argument
    • ๐Ÿšš now when many-to-many and one-to-many relation set to null all items from that relation are removed, just like it would be set to empty array
    • ๐Ÿ›  fixed issues with relation update from one-to-one non-owner side
    • โšก๏ธ now version column is updated on the database level, not by ORM anymore
    • โšก๏ธ now created date and update date columns is set on the database level, not by ORM anymore (e.g. using CURRENT_TIMESTAMP as a default value)
    • โšก๏ธ now InsertQueryBuilder, UpdateQueryBuilder and DeleteQueryBuilder automatically update entities after execution. This only happens if real entity objects are passed. Some databases (like mysql and sqlite) requires a separate query to perform this operation. โšก๏ธ If you want to disable this behavior use queryBuilder.updateEntity(false) method. โšก๏ธ This feature is convenient for users who have uuid, create/update date, version columns or columns with DEFAULT value set.
    • โšก๏ธ now InsertQueryBuilder, UpdateQueryBuilder and DeleteQueryBuilder call subscribers and listeners. You can disable this behavior by setting queryBuilder.callListeners(false) method.
    • ๐Ÿšš Repository and EntityManager method .findOneById is deprecated and will be removed in next 0.3.0 version. ๐Ÿ‘‰ Use findOne(id) method instead now.
    • ๐Ÿ“‡ InsertQueryBuilder now returns InsertResult which contains extended information and metadata about runned query
    • ๐Ÿ“‡ UpdateQueryBuilder now returns UpdateResult which contains extended information and metadata about runned query
    • ๐Ÿ“‡ DeleteQueryBuilder now returns DeleteResult which contains extended information and metadata about runned query
    • โšก๏ธ now insert / update / delete queries built with QueryBuilder can be wrapped into a transaction using useTransaction(true) method of the QueryBuilder.
    • โšก๏ธ insert, update and delete methods of QueryRunner now use InsertQueryRunner, UpdateQueryRunner and DeleteQueryRunner inside
    • โœ‚ removed deprecated removeById, removeByIds methods
    • โœ‚ removed deleteById method - use delete(id) method instead now
    • โœ‚ removed updateById method - use update(id) method instead now
    • โฌ†๏ธ changed snakeCase utility - check table names after upgrading
    • โž• added ability to disable transaction in save and remove operations
    • โž• added ability to disable listeners and subscribers in save and remove operations
    • โž• added ability to save and remove objects in chunks
    • โž• added ability to disable entity reloading after insertion and updation
    • class table inheritance functionality has been completely dropped
    • ๐Ÿ›  single table inheritance functionality has been fixed
    • @SingleEntityChild has been renamed to @ChildEntity
    • ๐Ÿšš @DiscriminatorValue has been removed, instead parameter in @ChildEntity must be used, e.g. @ChildEntity("value")
    • ๐Ÿšš @DiscriminatorColumn decorator has been removed, use @TableInheritance options instead now
    • ๐Ÿ”€ skipSync in entity options has been renamed to synchronize. Now if it set to false schema synchronization for the entity will be disabled. 0๏ธโƒฃ By default its true.
    • now array initializations for relations are forbidden and ORM throws an error if there are entities with initialized relation arrays.
    • ๐Ÿšš @ClosureEntity decorator has been removed. Instead @Entity + @Tree("closure-table") must be used
    • โž• added support for nested set and materialized path tree hierarchy patterns
    • ๐Ÿ’ฅ breaking change on how array parameters work in queries - now instead of (:param) new syntax must be used (:...param). ๐Ÿ›  This fixed various issues on how real arrays must work
    • ๐Ÿ”„ changed the way how entity schemas are created (now more type-safe), now interface EntitySchema is a class
    • โž• added @Unique decorator. Accepts custom unique constraint name and columns to be unique. Used only on as composite unique constraint, on table level. E.g. @Unique("uq_id_name", ["id", "name"])
    • โž• added @Check decorator. Accepts custom check constraint name and expression. Used only on as composite check constraint, on table level. E.g. @Check("chk_name", "name <> 'asd'")
    • ๐Ÿ›  fixed Oracle issues, now it will be fully maintained as other drivers
    • implemented migrations functionality in all drivers
    • โช CLI commands changed from migrations:create, migrations:generate, migrations:revert and migrations:run to migration:create, migration:generate, migration:revert and migration:run
    • ๐Ÿ”„ changed the way how migrations work (more info in #1315). Now migration table contains id column with auto-generated keys, you need to re-create migrations table or add new column manually.
    • entity schemas syntax was changed
    • โฌ‡๏ธ dropped support for WebSql and SystemJS
    • ๐Ÿ”€ @Index decorator now accepts synchronize option. This option need to avoid deleting custom indices which is not created by TypeORM
    • ๐Ÿ†• new flag in relation options was introduced: { persistence: false }. You can use it to prevent any extra queries for relations checks
    • โž• added support for UNSIGNED and ZEROFILL column attributes in MySQL
    • โž• added support for generated columns in MySQL
    • โž• added support for ON UPDATE column option in MySQL
    • โž• added SPATIAL and FULLTEXT index options in MySQL
    • โž• added hstore and enum column types support in Postgres
    • โž• added range types support in Postgres
    • 0๏ธโƒฃ TypeORM now uses { "supportBigNumbers": true, "bigNumberStrings": true } options by default for node-mysql
    • Integer data types in MySQL now accepts width option instead of length
    • junction tables now have onDelete: "CASCADE" attribute on their foreign keys
    • ancestor and descendant columns in ClosureTable marked as primary keys
    • unique index now will be created for the join columns in ManyToOne and OneToOne relations
  • v0.1.19 Changes

    • ๐Ÿ›  fixed bug in InsertQueryBuilder
  • v0.1.18 Changes

    • ๐Ÿ›  fixed timestamp issues