Request Postgres compatibility to support Flowable Engine: pg_catalog.set_config() #35108
Assignees
Labels
A-sql-pgcompat
Semantic compatibility with PostgreSQL
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
Comments
|
As with #35109, I'm pretty sure this query was issued by |
|
I noticed that flowable bypasses some errors in the app - might be one of the. Only one way to know.
… On Feb 21, 2019, at 1:01 PM, Roland Crosby ***@***.***> wrote:
As with #35109 <#35109>, I'm pretty sure this query was issued by pg_dump rather than the Flowable application.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#35108 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AlqpidsI7Ugg16a5qRjh0AB5WkfZ2HyNks5vPt8BgaJpZM4bGi_r>.
|
awoods187
added
the
C-enhancement
craig bot
pushed a commit
that referenced
this issue
Mar 7, 2019
35091: sql: rearchitecture ALTER TABLE RENAME, add support for renaming constraints r=knz a=knz Fixes #32555. For TypeORM compat, see discussion on #22298. Release note (sql change): This patch changes RENAME COLUMN to become a "table command", which can be used alongside other table commands in a single ALTER TABLE statement. This makes it possible to e.g. atomically add a computed column based on an existing column, and rename the columns so that the computed column "replaces" the original column. Release note (sql change): CockroachDB now supports ALTER TABLE RENAME CONSTRAINT for compatibility with PostgreSQL. This feature is limited to *named* constraints, where the name of the constraints is preserved in the table metadata. This currently includes CHECK, UNIQUE and FOREIGN KEY constraints, and does not include other constraints (DEFAULT, NULL etc) otherwise supported by PostgreSQL. For UNIQUE constraint, only supporting indexes that are not depended on by views can be renamed. 35121: sql: add support for pg_catalog.{current_setting,set_config} r=knz a=knz Fixes #35108. Needed for Flowable compatibility. Release note (sql change): The SQL built-in functions `pg_catalog.current_setting()` and `pg_catalog.set_config()` are now supported for compatibility with PostgreSQL. Note that only session-scoped configuration changes remain supported (`set_config(_, _, false)`). 35359: roachtest: backup: use AOST time slightly in the past r=mjibson a=mjibson Avoids problems where it's sometimes in the future according to the AOST logic. Fixes #34817 Release note: None 35371: sql: ensure column constraints are validated after SET for UPSERT r=knz a=knz Fixes #35040. Release note (bug fix): CockroachDB now properly applies column width and nullability constraints on the result of conflict resolution in UPSERT and INSERT ON CONFLICT. Co-authored-by: Raphael 'kena' Poss <knz@cockroachlabs.com> Co-authored-by: Matt Jibson <matt.jibson@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SELECT pg_catalog.set_config('search_path', '', false);
https://github.com/flowable/flowable-engine
The text was updated successfully, but these errors were encountered: