Skip to content

Releases: ForbesLindesay/atdatabases

@databases/websql@4.0.1

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/sqlite-sync@3.0.0

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/bigquery@1.0.1

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/sqlite-sync@2.0.0

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)

@databases/dataloader@1.1.0

20 Feb 13:57
66c0122
Compare
Choose a tag to compare

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/cache@1.1.1

20 Feb 13:57
66c0122
Compare
Choose a tag to compare

Bug Fixes

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

@databases/dataloader@1.0.1

19 Feb 17:37
b8ffa7a
Compare
Choose a tag to compare

Bug Fixes

  • Provide slightly stricter types for TypeScript (#318)

@databases/cache@1.1.0

19 Feb 17:37
b8ffa7a
Compare
Choose a tag to compare

New Features

  • Added Cache.deletePrefix(prefix). This lets you delete all keys with a given prefix from the cache. deletePrefix will throw an error if any of the keys are not serialized to a string. They can either already be strings, or you can use mapKey to convert them into strings if you want to use this method. (#317)

    Using this method with replication enabled will result in this new type of replication event:

    interface ReplicationDeletePrefixEvent {
      readonly kind: 'DELETE_PREFIX';
      readonly name: string;
      readonly prefix: string;
    }
  • You can now pass multiple keys to Cache.delete(...keys) to more efficiently delete multiple keys in a single call. (#317)

    Passing multiple keys with replication enabled will result in this new type of replication event:

    interface ReplicationDeleteMultipleEvent {
      readonly kind: 'DELETE_MULTIPLE';
      readonly name: string;
      readonly keys: unknown[];
    }

Bug Fixes

  • Provide slightly stricter types for TypeScript (#318)

@databases/pg-schema-print-types@4.5.0

12 Jan 18:57
e4d27b9
Compare
Choose a tag to compare

New Features

  • Partitioned tables support (#309)

@databases/pg-schema-introspect@4.2.0

12 Jan 18:57
e4d27b9
Compare
Choose a tag to compare

New Features

  • Partitioned tables support (#309)