v0.9.44

What's Changed

• [293] Implement FlatPostgresCollection#upsertAndReturn by @suddendust in #300

Full Changelog: 0.9.43...0.9.44

v0.9.43

What's Changed

• Upgrade pgjdbc to 42.7.11. Ref: https://nvd.nist.gov/vuln/detail/CVE-2026-42198 by @suddendust in #305

Full Changelog: 0.9.42...0.9.43

v0.9.42

What's Changed

• [290] Fix query shape for FlatPostgresCollection upsert and createOrReplace by @suddendust in #299
• [295] Make maxIdle and minIdle configurable by @suddendust in #296
• [Bugfix] [297] Add lastUpdatedTimestamp to all sub-doc update methods by @suddendust in #302

Full Changelog: 0.9.41...0.9.42

v0.9.41

What's Changed

• Add Collection#bulkUpdate(Map<Key, Collection> updates, ..) by @suddendust in #288

Full Changelog: 0.9.40...0.9.41

v0.9.40

What's Changed

• Change log to debug by @suddendust in #287

Full Changelog: 0.9.39...0.9.40

v0.9.39

What's Changed

• [FlatPostgresCollection] Implement bulkCreateOrReplaceReturnOlder + drop + Bugfix for delete(key) always returning true by @suddendust in #286

Full Changelog: 0.9.38...0.9.39

v0.9.38

What's Changed

• Add Collection#bulkCreateOrReplace by @suddendust in #284
• Implement Collection#search for FlatPostgresCollection by @suddendust in #285

Full Changelog: 0.9.37...0.9.38

v0.9.37

What's Changed

• Add Additional Telemetry to FlatPostgresCollection And SchemaRegistry by @suddendust in #282

Full Changelog: 0.9.36...0.9.37

v0.9.36

What's Changed

• Add MongoPostgresWriteConsistencyTest by @suddendust in #280

1. Fixes a bug in PostgresResultIteratorWithBasicTypes in which float4/real values were cast to strings. So say we have a field ratings with is a real field - It would appear as "4.3" in Document instead of 4.3 (Mongo behaves correctly so this fix is added for functional compatibility).
2. Added checks on the type of input in update parsers for fail-fast. This is inline with Mongo's behaviour.
3. Handle array fields properly in SET update parsers to parse them as a single value.
4. Fix the return behaviour of Collection#upsert for PG. Till now, it returns true if a new doc is created, false if it's updated. This is not inline with the contract or Mongo's behaviour - So now, it returns true if it succeeds.
5. Handle SET on entire JSONB columns properly.
6. Use CommonUpdateValidator for flat PG collections.

Full Changelog: 0.9.35...0.9.36

Release v0.9.35

What's Changed

• Timestamp Configs for FlatPostgresCollection by @suddendust in #274

Full Changelog: 0.9.34...0.9.35