Skip to content

Releases: ForbesLindesay/atdatabases

@databases/[email protected]

20 Aug 11:12
a70e81c
Compare
Choose a tag to compare

New Features

  • Thew new types.requireExplicitDefaults option will make columns that have a default value but are not marked as nullable required in the types generated for insert queries. (#340)

@databases/[email protected]

20 Aug 11:12
a70e81c
Compare
Choose a tag to compare

New Features

  • Added a new types.requireExplicitDefaults option. (#340)

    This new option will make columns required in the types generated for insert, even if the column has a default. The column will only be considered optional if it is marked as nullable.

@databases/[email protected]

16 Jun 12:35
2311288
Compare
Choose a tag to compare

New Features

  • Add an option to ignoreEnumValues. This will allow you to exclude certain values in the generated types for enums. This can be useful when you know that certain values never appear in your database, but cannot safely update the enum type in Postgres due to the migration being too costly. (#339)

@databases/[email protected]

16 Jun 12:35
2311288
Compare
Choose a tag to compare

New Features

  • Add an option to ignoreEnumValues. This will allow you to exclude certain values in the generated types for enums. This can be useful when you know that certain values never appear in your database, but cannot safely update the enum type in Postgres due to the migration being too costly. (#339)

@databases/[email protected]

16 Jun 12:34
2311288
Compare
Choose a tag to compare

New Features

  • Add an option to ignoreEnumValues. This will allow you to exclude certain values in the generated types for enums. This can be useful when you know that certain values never appear in your database, but cannot safely update the enum type in Postgres due to the migration being too costly. (#339)

@databases/[email protected]

10 Nov 21:25
cb1b783
Compare
Choose a tag to compare

Breaking Changes

  • Upgrade to mysql2 v3.x (#335)

@databases/[email protected]

25 Sep 19:19
5e389d5
Compare
Choose a tag to compare

Bug Fixes

  • Update dependency to fix errors installing on current node.js versions (#333)

@databases/[email protected]

25 Sep 19:19
5e389d5
Compare
Choose a tag to compare

Breaking Changes

  • bump better-sqlite3 to v11 (#331)

    Drop support for unsupported Node.js

@databases/[email protected]

24 Jun 15:51
d49f865
Compare
Choose a tag to compare

Bug Fixes

  • Update @google-cloud/bigquery dependency (#328)

    This drops support for node < version 14. We do not consider this to be a breaking change because @databases only supports versions of node.js that are maintained.

@databases/[email protected]

29 May 00:09
c55766e
Compare
Choose a tag to compare

Breaking Changes

  • Drop support for node v16 and update better-sqlite3 dependency to ^9.4.5 (#320)