pg-mem changelog

Changelog History

• v3.0.1 Changes

  August 06, 2024

  🔨 Mainly a refactoring #411, which now allows preparing statements before executing them.

  • ✅ Migration of unit tests to Bun
  • 👌 Supports binding query parameters
  • 👌 Support of postgres.js, fixes #386 and thanks to @smcclure17 to have attempted with #398
  • ⚠ Can now spawn a postgres server bound to a pg-mem instance, via db.adapter.bindServer() (using pg-server under the hood - ⚠️ NB: this is still very degraded, expect issues with complex use cases) => will help to solve #27, and fixes #360

• v2.9.1 Changes

  July 31, 2024

  forgot this one in the 2.9.0:

  • 👌 support mixed queries #410 thanks to @vacodoceo

• v2.9.0 Changes

  July 31, 2024

  🔄 Changes

  • 👍 adapter now support newer versions of Slonik
  • 🆕 newest version of mikoorm #361 thanks to @murbanowicz
  • 🛠 Fix pg-mem crashes when setval has three arguments instead of two #375 thanks to @neruchev
  • feat(functions): Added concat_ws #378 thanks to @Alexnortung
  • 👍 feat: Support clientConfigurationInput forwarding to slonik. #382 thanks to @ovstetun
  • export replaceQueryArgs$ from adapters.ts #385 thanks to @mmkal
  • feat(binary-operators): Added date minus date #388 thanks to @Alexnortung
  • 🛠 Fix AST coverage check error #389 thanks to @zookatron
  • ➕ Add GREATEST and LEAST functions #399 thanks to @Igggr

  💥 Breaking change

  • adapter.createSlonik():
    • now does not accept a number argument as query latency (accepts an object as argument)
    • must be awaited