Transaction isolation level not supported

[rhlsthrm]

Describe the bug

Running a simple transaction with isolation level breaks pg-mem.

     Error: 💔 Your query failed to parse.
This is most likely due to a SQL syntax error. However, you might also have hit a bug, or an unimplemented feature of pg-mem.
If this is the case, please file an issue at https://github.com/oguimbal/pg-mem along with a query that reproduces this syntax error.

👉 Failed query:

    START TRANSACTION ISOLATION LEVEL SERIALIZABLE;

💀 Syntax error at line 1 col 19:

  START TRANSACTION ISOLATION
                    ^
Unexpected word token: "isolation". Instead, I was expecting to see one of the following:

    - A "semicolon" token

To Reproduce

START TRANSACTION ISOLATION LEVEL SERIALIZABLE;

pg-mem version

"version": "2.6.3",

My PG library Zapatos uses isolation levels and it would be really useful to have this supported.

[MyNameIsOka]

I just started setting up pg-mem for our project and ran into the same error.
Is there anything I can do as a workaround (except ditching isolation)?

[rhlsthrm]

I just started setting up pg-mem for our project and ran into the same error. Is there anything I can do as a workaround (except ditching isolation)?

This was a dealbreaker for me so I moved off this project and I'm running Postgres directly in our unit tests in CI.

[MyNameIsOka]

Thank you for the quick reply! Sad to hear this as this repo looks quite convenient.

[rhlsthrm]

It is quite convenient if your PG queries are quite basic I think.

[smcclure17]

Having this same issue sadly, I was hoping to use a pg-mem adapter with Drizzle ORM, but the Drizzle migrations cause this issue.

It looks like this library uses https://github.com/oguimbal/pgsql-ast-parser to parse SQL queries. There's an open issue for supporting SET TRANSACTION ... queries, but it's been open for a long time oguimbal/pgsql-ast-parser#76