Name | Modified | Size | Downloads / Week |
---|---|---|---|
Parent folder | |||
doltgresql-windows-amd64.7z | 2025-02-17 | 21.2 MB | |
doltgresql-windows-amd64.zip | 2025-02-17 | 37.6 MB | |
doltgresql-darwin-arm64.tar.gz | 2025-02-17 | 39.9 MB | |
doltgresql-darwin-amd64.tar.gz | 2025-02-17 | 41.5 MB | |
doltgresql-linux-arm64.tar.gz | 2025-02-17 | 38.9 MB | |
doltgresql-linux-amd64.tar.gz | 2025-02-17 | 41.5 MB | |
0.17.1 source code.tar.gz | 2025-02-17 | 8.6 MB | |
0.17.1 source code.zip | 2025-02-17 | 9.9 MB | |
README.md | 2025-02-17 | 2.7 kB | |
Totals: 9 Items | 239.0 MB | 0 |
Merged PRs
doltgresql
- 1206: Added loop structures and label support
This adds the rest of the "non-FOR" loops, along with loop control flow and labels. I also noticed that we weren't using
OperationSizeForStatements
, which will properly calculate offsets for theGoto
operations, so I fixed that. Just so happened that our tests weren't running into the issue. - 1200: Fix backup restore auth for super user Dolt PR: https://github.com/dolthub/dolt/pull/8860
- 1199:
NULL
support in PL/pgSQL We get support forNULL
statements frompg_query_go
since it automatically filters them out. This change adds a test of their usage. - 1197:
WHILE
statements in PL/pgSQL Adds basic support forWHILE
statements in PL/pgSQL. No support for labels yet. - 1196: Fixed CREATE FUNCTION not executing some statements
Simple bug, but was difficult to spot. Some statements work without needing to advance the returned
RowIter
, while others require advancing it. I changed it so that we're always advancing the iterator. I also unskipped the skipped tests, and removed the temporary one since the original now works. - 1193: Added SELECT ... INTO and PERFORM, plus bugfixes Hoped to get a few more statements in, but there's an issue where some statements that are ran from the interpreter are seemingly being discarded. It was a roadblock even for these two, hence the skipped tests. That's the next thing I'mma look into, as it's a pretty big issue (especially since there's no error, just no effect which is even worse).
- 1171: Bug fixes for using various types in keys This PR allows various types to be used in keys that were not possible before. This comes down to two things: 1) Swap out the validateCreateTable analyzer rule 2) Change the determination for the max width of a type to be more accurate, which influences whether we choose standard extended encoding or extended address encoding 3) Alter the way we determine the encoding type for extended columns in keys to more closely match the non-key case (https://github.com/dolthub/dolt/pull/8817) This PR also has a couple small regressions in tests. I'm punting on these because we're about to completely overhaul how we store these types (to implement toast semantics).