Merged
Conversation
chenrui333
approved these changes
Feb 11, 2026
Contributor
|
🤖 An automated task has requested bottles to be published to this PR. Caution Please do not push to this PR branch before the bottle commits have been pushed, as this results in a state that is difficult to recover from. If you need to resolve a merge conflict, please use a merge commit. Do not force-push to this PR branch. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Created by
brew bumpCreated with
brew bump-formula-pr.Details
release notes
This adds the remaining
ALTER TABLEstatements that have special hooks for table types.This PR is mostly tests. See Various bug fixes for checking foreign key constraints during merge dolthub/dolt#10418 for most of the logic.
information_schema.constraint_column_usageviewDepends on allow Doltgres to add more information schema tables dolthub/go-mysql-server#3416
information_schema.constraint_column_usagesystem view as tableintto be casted inregtypeasint4Integration tests for sqlAlchemy.
Pretty similar to our standard dolt sqlAlchemy tests, with a couple of differences. I used the newer version of sqlAlchemy (2.0.46) and had to make some setup changes using features that were introduced in 2.x builds.
psycopg2 seems to convert row results into python lists as well so the expected results had to be changed. I couldn't find confirmation but it seems like that would be the expected behavior (from what claude found).
This fixes the other issues brought up in:
This also adds support for column access, which is used by the
UPDATEstatement when a new column is added.I found that starting from version 0.54.4 (after #2061), binaries for Windows are built with empty names. This PR should fix that.
Adds regression tests using psycopg2 for fix from Bug fix: don't send RowDescription message with each spooled batch of rows dolthub/doltgresql#2216
This is a fix for:
I've added a skipped test to verify that the syntax error portion is fixed, however we don't yet support expression index attributes, so the test overall fails. However, the issue only covers the syntax portion which we're addressing here.
I accidentally merged dolthub/dolt#10227: add dolt_status_ignored dolt system table dolthub/doltgresql#2196 while it contained a replace directive pointing to a fork of Dolt.
This PR contains the actual dolt version bump.
pg_catalogis always implicitly the first element on thesearch_path, unless it's explicitly included elsewhere:https://www.postgresql.org/docs/current/ddl-schemas.html#DDL-SCHEMAS-CATALOG
We weren't implementing this behavior, causing us to fail to resolve
::regclassexpressions in some cases with a "no such relation" error for allpg_catalogtables.This fix isn't complete, because the same logic should also apply to all table lookups. i.e. users should be able to create a table named
pg_class, and what the namepg_classresolves to depends on whether thepg_catalogschema is explicitly present in thesearch_pathand where it is relative to the user's other schemas. That's a pretty obscure bug and is left unaddressed for now.Fixes filter with
'pg_class'::regclassproducesrelation "pg_class" does not existerror whenEvalis called duringsimplifyFiltersdolthub/doltgresql#2217Ensure that
RowDescriptionmessages are sent only once, at the beginning of query results. Sending multiple times, at the start of each batch of spooled rows, breaks some clients, such as psycopg2.Note that this wasn't causing a problem in the other clients we use for testing. To properly regression test this, we should follow up with adding a test suite for psycopg2.
Related to psycopg2 support dolthub/doltgresql#2143
RETURNS TABLESummary
Add adapter and test expectations for the newdolt_status_ignoredsystem table from dolthub/dolt#10227.This table provides the same information as
dolt_statusplus an additionalignoredboolean column.Changes
DoltgresDoltStatusIgnoredTableAdapterinserver/tables/dtables/status_ignored.goserver/tables/dtables/init.gotesting/go/pgcatalog_test.gotesting/go/sequences_test.goDependencies
Closed Issues
'pg_class'::regclassproducesrelation "pg_class" does not existerror whenEvalis called duringsimplifyFiltersView the full release notes at https://github.com/dolthub/doltgresql/releases/tag/v0.55.0.