Merged PRs

doltgresql

• 2132: Fixed JSONB extended value error
  Fixes the issue:
  • #2127
• 2128: Added some hooks for DROP TABLE
  This adds support for ensuring that dropping a table while using table types doesn't outright put the database in an unusable state. There are many more hooks that need to be implemented across the board, but these are relatively straightforward ones for a common case of dropping a table, function, or procedure that uses them.
  This also adds support for DROP PROCEDURE, which I apparently overlooked when adding procedure support in general. Lastly, this adds support for the serialization and deserialization of values within columns that use table types. While it was previously possible to create tables that use table types, it wasn't possible to read from those tables (and writing to them just wrote useless data that couldn't be removed).
  You'll notice that error messages involving procedures return "function" instead of "procedure". Postgres calls them functions in their error messages, so we're replicating that.
• 2125: Changed configuration file for function passing
  In a nutshell, our internal repository for handling Hosted Doltgres only needs to include the configuration file, however recent changes added more packages that were referenced from our servercfg package. As our internal repository wasn't configured to handle these additional packages (which essentially requires building the entirety of Doltgres), it broke the existing workflow. To workaround this, I've moved the "details" of the configuration to its own package (named cfgdetails), and that will be referenced by our internal repository. Elsewhere in Doltgres, we still refer to servercfg, which has a wrapper struct around our details.
  The wrapper is needed as we cannot store a field that contains the overrides on the struct itself. Our YAML deserialization function does not honor ignored fields (which are supposed to work using yaml:"-") and is therefore panicking. Instead, the wrapper declares its own Overrides() function that overrides the function within cfgdetails.
• 2123: Bug fix: ensure OR expressions on a single table use an index when possible
  This fixes the performance regression in select_random_ranges, which uses BETWEEN .. OR BETWEEN .. in its filters.
  Requires dolthub/go-mysql-server#3347

Closed Issues

• 2097: auth.db, unable to configure path for "authFileName" file
• 2100: DOLTGRES_DB environment variable isn't respected

Merged PRs

doltgresql

• 2108: typo preventing release version from getting to docker push workflow
• 2107: added another function stub
• 2106: Fixed issue #2097
  This fixes
  • #2097
• 2093: remove doltgres index implementation, various bug fixes
  Companion PRs:
  • dolthub/go-mysql-server#3334
  • dolthub/dolt#10184
    This removes the custom index logic Doltgres was using, and fixes many bugs and incompatibilities that were causing the Dolt index logic to not work correctly in the first place.
• 2009: Tables as types
  Related PRs:
  • dolthub/dolt#10140
  • dolthub/go-mysql-server#3303

Closed Issues

• 2097: auth.db, unable to configure path for "authFileName" file
• 2100: DOLTGRES_DB environment variable isn't respected

Merged PRs

doltgresql

• 2102: Set the default DB from the DOLTGRES_DB user var
  Fixes #2100
• 2091: added MetricsJwksConfig() stub
• 2089: updated readme
• 2068: Fix Doltgres and Dolt authentication and system table compatibility
  Companion dolthub/dolt#10159
  • Add SUPERUSER authentication for generated Dolt procedure callables for SELECT statements.
  • Remove Dolt procedures from CALL statements.
  • Add adapters.TableAdapter for dolt_status system table to handle type change in Dolt due to a limitation with the MySQL protocol in distinguishing Booleans.
  • Add params column in the pgcatalog table for dolt_backups recent changes.
  • Add extensive suite of _go.ScriptTest for Dolt procedure authentication testing in Doltgres.
  • Add support to run local file system tests by setting flag in _go.ScriptTest for new tests. Some procedures require this because some Noms functions use os package calls for directory writes instead of the filesys package.

Closed Issues

• 2100: DOLTGRES_DB environment variable isn't respected

Merged PRs

doltgresql

• 2076: push to docker hub
• 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"

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

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

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

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

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

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