Richard Wheeldon

Add support for backslash commands (e.g. \ir \o)

1

Whilst not strictly SQL, the postgres shell supports a lot of backslash commands which get used in all sorts of scripts. Some of the most useful being: \i - execute...

Doesn't work with regex rules in check constraints

1

# Describe the bug I have a number of tables with regex-based check constraints to prevent garbage from being put into the DB. Unfortunately, pg-mem doesn't seem to like them....

check-in constraints assume not-null unlike postgres

1

# Describe the bug If I have a check constraint which considers values in a list and use this in Postgres, it works if the value is null. In pg-mem...

Throws EISDIR error when running deploy

1

Affects v3 pre-release. Throws an error like this when I run serverless deploy: ``` Error: EISDIR: illegal operation on a directory, unlink '//.build/node_modules' ``` Mentioned in https://github.com/serverless/serverless/issues/10326#issuecomment-1783582404 - but this...

Add support for exists / not exists

1

# Describe the bug Exists and not exists should be treated as basic join operations but when using them we get unsupported function errors ``` ERROR: function exists(integer[]) does not...

# Describe the bug Trying to do an insert based on a CTE (with) and I get the following: ``` 🔨 Not supported 🔨 : "WITH" nested statement with query...

# Describe the bug I have a query with a join and some boolean logic. with an in(). Somehow this is tripping up an edge case in pg-mem. I've produced...

# Describe the bug Common Table Expressions (CTEs) or "with" blocks are supported by postgres and pg-mem. See https://www.postgresql.org/docs/current/queries-with.html for background The materialized keyword has significant impacts on performance in...

Using "using" on joins leads to wrong "ambiguous reference" errors

1

# Describe the bug Doing a join with "using" for a column ID implies it's not ambiguous - it doesn't matter which one you pick because they're the same. Postgres...

# Describe the bug I can run create schema commands but drop ones don't work. In particular drop if exists doesn't work but if I run create schema twice with...