0.54.4

Merged PRs

doltgresql

• 2082: debugging
• 2080: debug
• 2076: push to docker hub
• 2075: Fixed typo in release script
• 2073: Fix release script
• 2061: Dockerfile
  Also: configure the super user and password with new env vars:

  DOLTGRES_USER
  DOLTGRES_PASSWORD

Closed Issues

• 2060: Error parsing time "America/Los_Angeles"

0.53.6

Merged PRs

doltgresql

• 2069: /{Dockerfile,.dockerignore}: some tweaks
• 2067: Fixed timestamp replication
  This fixes the two issues found in
  • #2060
    The first was that replication was incorrectly formatting timestamp values, so now we bypass it and use the returned time strings directly. The second was that we had America/Los_Angeles hardcoded as the parameter value, and in some cases we would ignore the local timezone and use the parameter value. Now, we default the parameter value to the local as well.

Closed Issues

• 2049: SyntaxError: Bad control character in string literal in JSON

0.53.5

Merged PRs

doltgresql

• 2055: Fixed Issue #2049
  This fixes the following PR:
  • #2049
    At its core, our JSON parsing libraries (both go-json and the internal json packages) replace binary escape sequences (\n, \t, \r) with their ASCII byte replacements, which doesn't mirror what Postgres clients expect (that the binary representation is preserved). This extends to our testing framework as well, so this also adds raw byte comparisons for testing.
• 2047: updated README
  Also cleaned up some leftover dolt typos in install.sh

Closed Issues

• 2030: Drizzle relational query fails with BigInt error

0.53.4

Merged PRs

doltgresql

• 2041: Fixed a couple issues with prepared statements
  This PR addresses a couple issues discovered by a customer working with the Drizzle ORM
  1. Literals in LIMIT statements were being inappropriately flagged as invalid when they appeared in subqueries
  2. Bindvars in ON CONFLICT clauses were not being handled correctly
     Fixes #2030
• 2038: add metrics tls param to the server config
• 2036: Another attempt at install.sh

Closed Issues

• 2030: Drizzle relational query fails with BigInt error

0.53.1

Merged PRs

doltgresql

• 2022: Bug fixes for null handling in prepared statements
  Null values given to prepared statements did not work, resulting in various errors and incorrect behavior. This fixes the issue and also addresses similar null-handling bugs in the testing framework discovered while testing.
  Fixes #2016
• 2014: Keep branch tracking enabled in doltgres

Closed Issues

• 2016: Cannot insert NULL into JSONB column: "cannot scan NULL into *string" error
• 1990: Unable to run subsequent drizzle migrations

0.53.0

Merged PRs

doltgresql

• 1996: bug fix for sequence name generation
  Fixes #1990
• 1993: Index join performance
  This PR fixes a couple issues that were preventing indexes from being used in join planning:
  • Swap SplitConjunction out in memo package to correctly handle doltgres expressions
  • Use DoltgresTable in JoinNode to allow indexing consideration during joins
    This work uncovered a bug in index use during joins, see new skipped test. Followup work required to fix.
    Also fixes a bug in the pg_constraint table output for foreign keys.
    Companion PR:
    dolthub/go-mysql-server#3289
• 1991: TupleDesc as pointer
  Companion PR: dolthub/dolt#10025

Closed Issues

• 1990: Unable to run subsequent drizzle migrations
• 659: unable to reuse the same table name and column name for serial type after the old table is dropped

0.52.4

Merged PRs

doltgresql

• 1983: check for power(x, 0) for decimal types
  The shopspring decimal package (https://pkg.go.dev/github.com/shopspring/decimal) changed from 1.3.1 -> 1.4.0, which came with some behavior differences.
  Notably, raising a decimal to exponent 0 does not result in 1.0 like it used to.

Closed Issues

0.52.3

Merged PRs

doltgresql

• 1942: Better in memory index iterator implementation
  As discussed in my recent blog. Faster and no resource leaks.
• 1940: Indexes for pg_namespace
• 1938: Added support for CREATE PROCEDURE
  This adds support for CREATE PROCEDURE, which is necessary for making progress on dumps.
• 1928: More dump-related fixes
  These are more fixes related to failing imports. In a nutshell, our function testing is fairly barebones, and there were several panics occurring due to incorrect assumptions and a lack of test variety (for example, the date 2025-01-02 being taken as integer subtraction rather than a date, exceptions not handling variables correctly, etc.). Still too many imports failing overall to enable them in CI, but this gets us a step closer.
• 1924: indexes for pg_constraint
  Also added domains and their checks to the output of pg_constraint.

Closed Issues