5 ms·

I feel obliged to namedrop Zapatos here, another postgres JS client with a remarkably similar design (sql in template strings), but fully typesafe. If TypeScrip

I feel obliged to namedrop Zapatos here, another postgres JS client with a remarkably similar design (sql in template strings), but fully typesafe. If TypeScript is your thing, you might appreciate it: https://jawj.github.io/zapatos/ https://jawj.github.io/zapatos/ Personally I feel it’s one of the best designed (and documented) TS libraries out there and I’m sad it’s not very well known.

willtemperley 3y ago
At first glance Zapatos doesn't appear to be Cloudflare workers compatible though I'd love to be corrected.
- gmac 3y ago
  It should be, now that pg runs fine there. If it’s not, please file an issue! It also works with @neondatabase/serverless on platforms without TCP connections (though it’s on my TODO list to make this less fiddly): https://github.com/neondatabase/neon-vercel-zapatos https://github.com/neondatabase/neon-vercel-zapatos
9dev 3y ago
Seconded. The lateral join features in combination with the shortcut functions make it exceptionally easy to build backends with actual SQL, without compromising on ease of use.
- oulipo 3y ago
  Does that work also with Postgres-compatible backends like Bigquery et al ?
  - gmac 3y ago
    It relies on pg (node-postgres) to talk to Postgres, so it should work with anything pg can talk to.
xctr94 3y ago
We had to abandon Zapatos because a) it doesn’t support multiple schemas; b) the types wouldn’t always be very readable. PgTyped was the alternative, and 2 years later I’m very glad we made the switch.
- Exuma 3y ago
  What do you mean multiple schemas ? What is an example of a non readable type?
  - pimeys 3y ago
    Like this, it's pretty common way to use Postgres (with multiple schemas): CREATE SCHEMA a; CREATE SCHEMA b; CREATE TABLE a.foo (id SERIAL PRIMARY KEY); CREATE TABLE b.foo (id SERIAL PRIMARY KEY);
  - xctr94 3y ago
    I didn’t know support for schemas had landed, but the docs still seem obtuse for joins and upserts. Compared to plain SQL files in PgTyped — which admittedly needs some annotations to work, and lacks transactions —, I find the lateral joins in Zapatos really verbose and ugly. Lots of extra parameters too. Which isn’t to say it’s not a great tool! You pick what you like :)
    - alde 3y ago
      Glad you are liking pgTyped. Transactions are supported as pgTyped is just a thin wrapper around node-postgres: https://github.com/adelsz/pgtyped/discussions/448 https://github.com/adelsz/pgtyped/discussions/448
      - xctr94 3y ago
        Ah, I meant having a single transaction in a SQL file, as that’s how we’re using it. So having multiple queries with a BEGIN and COMMIT wrapping them.
- hhfdsbvc 3y ago
jokesterfr 3y ago
Do you know why zapatos relies on pg and not PostgresJs?

willtemperley 3y ago

At first glance Zapatos doesn't appear to be Cloudflare workers compatible though I'd love to be corrected.

gmac 3y ago
It should be, now that pg runs fine there. If it’s not, please file an issue! It also works with @neondatabase/serverless on platforms without TCP connections (though it’s on my TODO list to make this less fiddly): https://github.com/neondatabase/neon-vercel-zapatos https://github.com/neondatabase/neon-vercel-zapatos

9dev 3y ago

Seconded. The lateral join features in combination with the shortcut functions make it exceptionally easy to build backends with actual SQL, without compromising on ease of use.

oulipo 3y ago
Does that work also with Postgres-compatible backends like Bigquery et al ?
- gmac 3y ago
  It relies on pg (node-postgres) to talk to Postgres, so it should work with anything pg can talk to.

xctr94 3y ago

We had to abandon Zapatos because a) it doesn’t support multiple schemas; b) the types wouldn’t always be very readable. PgTyped was the alternative, and 2 years later I’m very glad we made the switch.

Exuma 3y ago
What do you mean multiple schemas ? What is an example of a non readable type?
- pimeys 3y ago
  Like this, it's pretty common way to use Postgres (with multiple schemas): CREATE SCHEMA a; CREATE SCHEMA b; CREATE TABLE a.foo (id SERIAL PRIMARY KEY); CREATE TABLE b.foo (id SERIAL PRIMARY KEY);
- xctr94 3y ago
  I didn’t know support for schemas had landed, but the docs still seem obtuse for joins and upserts. Compared to plain SQL files in PgTyped — which admittedly needs some annotations to work, and lacks transactions —, I find the lateral joins in Zapatos really verbose and ugly. Lots of extra parameters too. Which isn’t to say it’s not a great tool! You pick what you like :)
  - alde 3y ago
    Glad you are liking pgTyped. Transactions are supported as pgTyped is just a thin wrapper around node-postgres: https://github.com/adelsz/pgtyped/discussions/448 https://github.com/adelsz/pgtyped/discussions/448
    - xctr94 3y ago
      Ah, I meant having a single transaction in a SQL file, as that’s how we’re using it. So having multiple queries with a BEGIN and COMMIT wrapping them.
hhfdsbvc 3y ago

jokesterfr 3y ago

Do you know why zapatos relies on pg and not PostgresJs?