-
# Describe the bug
Not sure if it is a bug or just something pg-mem doesn't support yet.
```
QueryError: select "devices".*, COALESCE(json_agg(DISTINCT acl_rules.id) FILTER (WHERE acl_rule…
-
# Describe the bug
Pg-mem returns `bytea` types with utf8 encoding, when it should use hex encoding, as per https://www.postgresql.org/docs/current/datatype-binary.html
I think the offending cod…
-
Investigate [Prisma](https://www.prisma.io/) support
-
## Problem
Currently Prisma does not have support for any sort of in-memory postgres database adapter. This makes testing harder and requires an actual postgres instance running for any sort of int…
-
# Describe the bug
Query fails to parse if trying to use a function for a generated column
```
💔 Your query failed to parse
This is most likely due to a SQL syntax error. However, you might al…
-
# 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 mi…
-
How could we support the `SAVEPOINT` statement?
-
**Describe the bug**
A clear and concise description of what the bug is.
When I use export FMOE_FASTER_SHADOW_ENABLE=1 and export FMOE_FASTER_SCHEDULE_ENABLE=1 to turn on Smart schedule,and bash exa…
-
# Describe the bug
The Postgres documentation specifically mentions that default values should be evaluated when a record is inserted, not when the table is created: https://www.postgresql.org/docs…
-
# Describe the bug
Just trying to use pg-mem in a Next.js app (importing pg-mem in our in-house library that is used in our Next.js app), the Next.js app fails to start in both dev and prod mode, w…
gthb updated
6 months ago