You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1731: Fixed sequences breaking some statements
When sequences were added, some commands failed to run (reporting table not found errors). This was due to sequence names being returned in locations that Dolt expected only table names, so the returned error reflected that the table could not be found. The relevant fix is in Dolt, with this primarily adding testing.
Relies on:
1724: Fixed merge issues
There was a merge bug that was preventing a few more tests from passing, which has been fixed on the Dolt side. Additionally, serialization of conflicts have been updated, and I didn't bump the version number since we don't have a release with conflict support, so it should be safe to do so. This also fixes a few additional bugs that were hidden behind the aforementioned merge bug.
Relies on:
1710: #1708 - Fix query converter crash on boolean literals
Fixes #1708
Query converter was panicking with "unhandled type: sqlparser.BoolVal" when encountering boolean literals like FALSE in CREATE TABLE statements. This was blocking UNION column mapping tests from dolthub/dolt#9628. Postgres CI docker container is also end of life, switched next LTS ver of Ubuntu 22.04.
1671: add plus and minus functions for time, date types
Used Claude
1657: add missing syntax for date parsing and support srf used in table fun…
…ction syntax
Depends on: dolthub/go-mysql-server#3105
1647: Root Object Conflicts & Merging
This implements root object conflict resolution and merging capabilities. Root objects are only used by Doltgres, and they're the underlying type for sequences, triggers, interpreted functions, etc. Each root object defines its own diff and merge strategy, with Dolt handling all of the internal logic (such as ensuring conflicts are resolved, etc.). The same general approach was used to create root objects in the first place (where each defines its own handling logic, while Dolt manages their storage on the root value). As with Dolt, we make use of the dolt_conflicts_TABLENAME structure, which includes the ability to delete conflicts and update the root objects by inserting into the our_value column: https://docs.dolthub.com/sql-reference/version-control/dolt-system-tables#dolt_conflicts_usdtablename
Requires: