Merged PRs

doltgresql

• 2601: Fixes 2462, 2574, 2579, 2604 This fixes:
• https://github.com/dolthub/doltgresql/issues/2462
• https://github.com/dolthub/doltgresql/issues/2574
• https://github.com/dolthub/doltgresql/issues/2579
• https://github.com/dolthub/doltgresql/issues/2604 The array concatenation functions are tested independently in existing tests with the exception of array_prepend, which is new (hence the lack of new tests for those functions).
• 2597: allow SELECT; and column name for cast result fix
• 2596: Fixed user/pass issue for initialization scripts, added docs Fixes https://github.com/dolthub/doltgresql/issues/2300
• 2588: Add support for UTF8 chars in identifiers Enables use of UTF8 chars in identifiers, matching PostgreSQL behavior. Related to https://github.com/dolthub/doltgresql/issues/2580
• 2587: add a stack trace to recovered panic
• 2583: DEALLOCATE ALL Fixes https://github.com/dolthub/doltgresql/issues/2575
• 2570: support nested block statements and call statement in plpgsql
• 2562: Support using same parameter multiple times Right now we always don't allow a query to use the same parameter in multiple locations. Technically that should always be allowed and then we'll fail later down the line if you're trying to bind a parameter and compare it to something with an incompatible type. But the error messages we have if I just completely remove the check are a little ugly, so I added some code to our function that handles the types of parameters by breaking if you try to use a parameter as multiple incompatible types within the same query. So for instance the query: select * from table where column_int = $1 and column_float4 = $1 should be fine because integer/int4 is compatible with float4. But the query: select * from table where column_text = $1 and column_int = $1 will error because text and integer/int4 are not compatible.
• 2558: fix type resolution in select of create view stmt

Closed Issues

• 2604: dolt_merge fails with "at or near \"<index_name>\": syntax error" on 3-way merge when table has both UNIQUE INDEX and a column with DEFAULT clause
• 2579: Array operator || not implemented
• 2574: SELECT 'now'::timetz --> spurious error
• 2462: PostgreSQL Compatibility: SET TIME ZONE '<offset>' fails with invalid value parameter error
• 2578: Enums: reported column attribute is incorrect
• 2573: Empty SELECT --> spurious error
• 2146: pg_tables system table: tableowner column is incorrect
• 2300: Docker entrypoint exec_sql hardcodes postgres/password credentials, ignoring DOLTGRES_USER/DOLTGRES_PASSWORD
• 2580: UTF8 table names not supported
• 2575: DEALLOCATE ALL --> spurious error
• 2250: Feature request: Support indexing expressions on columns
• 2546: SELECT 'foo' --> invalid OID 705
• 2547: concat('', NULL, '') incorrectly returning null string
• 2548: Timezone parser does not accept PostgreSQL-accepted formats (time zone offset)