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
#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
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