Show HN: Prisma Postgres. Runs on bare metal and unikernels

Re:Show HN: Prisma Postgres. Runs on bare metal and unikernels by jjice on Saturday November 02, 2024 @06:51PM (#42029804)

I'm not super well versed in this domain, but I believe Postgres columns need to be wrapped in double quotes to respect case, or else they're all treated as lower, or something along those lines?

[ Parent | on HN ]

Re:Show HN: Prisma Postgres. Runs on bare metal and unikernels by dboreham on Saturday November 02, 2024 @06:53PM (#42029828)

I seem to recall it's a SQL thing, not just PostgreSQL, although Oracle might not follow the spec. Definitely annoying.

[ Parent | on HN ]

Re:Show HN: Prisma Postgres. Runs on bare metal and unikernels by Shorn on Saturday November 02, 2024 @07:05PM (#42029890)

For MySQL, it can depend on the OS! https://dev.mysql.com/doc/refman/8.0/en/identifier-case-sens...

[ Parent | on HN ]

Re:Show HN: Prisma Postgres. Runs on bare metal and unikernels by evanelias on Saturday November 02, 2024 @07:33PM (#42030023)

That's largely only true for schema names and table names, not all identifiers.

The original root cause was having schemas backed by directories, and table definitions backed by .frm files. So on a case-insensitive filesystem like on Windows or MacOS, MySQL enables corresponding case-insensitivity logic for the affected types of identifiers.

For a deeper dive, see my post https://www.skeema.io/blog/2022/06/07/lower-case-table-names...

[ Parent | on HN ]

Re:Show HN: Prisma Postgres. Runs on bare metal and unikernels by mattashii on Saturday November 02, 2024 @07:03PM (#42029885)

Yes, SQL does specify case-folding unless quoted.

However, the SQL standard prescribes the case to be folded to uppercase, while PostgreSQL folds to lowercase.

[ Parent | on HN ]