@databases/[email protected]

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]

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]

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]

Breaking Changes

• Upgrade to mysql2 v3.x (#335)

@databases/[email protected]

Bug Fixes

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

@databases/[email protected]

Breaking Changes

• bump better-sqlite3 to v11 (#331)

  Drop support for unsupported Node.js

@databases/[email protected]

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]

Breaking Changes

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

@databases/[email protected]

New Features

• You can pass multiple keys to cachedFn.cache.delete(...keys) now for both dedupeAsync and dedupeSync. If the underlying cache/map accepts a ... spread parameter, the array of keys will be passed directly to the undelrying map. Otherwise .delete will be called multiple times on the underlying map. (#319)

• A new method has been added for cachedFn.cache.deletePrefix(prefix) for both dedupeAsync and dedupeSync. (#319)

  If the map used as the cache is a MultiKeyMap, deletePrefix takes any sub-path for the key. e.g. MultiKeyMap<[string, number, string]> would result in a deletePrefix function that accepts [string] | [string, number] as the key.

  If the map used as the cache has a deletePrefix method, the prefix is passed directly to that method.

  If the keys are serialized to a string, deletePrefix accepts a string and will delete keys where the serialized value matches that string.

@databases/[email protected]

Bug Fixes

• If 0 parameters are passed to .delete it will no longer generate a DELETE_MULIPLE event for replication. (#319)