-
Thank you for this extension. I prefer this one over any others I've used so far.
That said, I'm coming across an issue that's preventing me from using it for formatting procedural SQL. I'm trying …
-
The scope of work only includes minimum needed to support how dynamic SQL is used in a customer’s Stored Procs
Jira issue: CRDB-33968
Epic CRDB-37715
-
lowerstr: dict_snowball vector
CurrentMemoryContext: dict_snowball
error_context_stack: vector plpgsql
-
#110709 added initial support for the PLpgSQL `OPEN` statement, which allows a PLpgSQL routine to open a cursor that can be interacted with in the same ways as one created by SQL `DECLARE ... CURSOR` …
-
### Search before asking
- [X] I searched the [issues](https://github.com/sqlfluff/sqlfluff/issues) and found no similar issues.
### What Happened
I really want to use sqlfluff in my system…
-
It is an Oracle specific feature and there is no exact equivalent capability in Postgres. The scope of work only includes support feasible work-around to unblock a customer's use cases.
Jira issue:…
-
Any way to parse plpgsql?
It parses correctly CreateFunctionStmt, but since function declaration itself is a string literal it is "correctly" parsed as a string.
Would be great if it could detect…
-
When a PL/pgSQL RAISE statement is executed, its message is immediately flushed to the client in order to mirror postgres behavior. However, this interferes with transaction retries, because the trans…
-
It is an Oracle specific feature and there is no exact equivalent capability in Postgres. The scope of work only includes support feasible work-around to unblock a customer's use cases.
Jira issue:…
-
Postgres PLpgSQL allows for `RETURN NEXT` and `RETURN QUERY` syntax in order to return multiple rows from a PLpgSQL set-returning function. See the section `43.6.1.2. RETURN NEXT And RETURN QUERY` in …