postgres

I just started a project and chose this stack: - SSR SvelteKit with Hydration (https://github.com/sveltejs/kit) - PostgreSQL database server - Postgres.js - PostgreSQL client for Node.js (https://github.com/porsager/postgres) - Migration powered by graphile-migrate (https://github.com/graphile/migrate) - PostgreSQL Row-Level Security (https://www.postgresql.org/docs/16/ddl-rowsecurity.html) - svelte-headlessui (https://github.com/rgossiaux/svelte-headlessui) - sveltekit-i18n (https://github.com/sveltekit-i18n/lib) - TailwindCSS (https://tailwindcss.com/) - Superforms (https://superforms.rocks/) - sveltekit-flash-message + svelte-french-toast (https://github.com/ciscoheat/sveltekit-flash-message + https://github.com/kbrgl/svelte-french-toast) Tooling : - asdf (https://asdf-vm.com/) - Docker and Docker Compose - NodeJS - pnpm - Jest for uni

Thanks Pier! Your comment saved me some frustration here :-D https://github.com/porsager/postgres/discussions/627#discuss...

reposting my comment on its benchmarks: On what makes it postgres.js faster, from author himself: > it seems Postgres.js is actually faster than, not only pg, but of any driver out-there - https://github.com/porsager/postgres/discussions/627 - https://porsager.github.io/imdbench/sql.html

Looks like named prepared statements can be disabled by setting "prepare" to false in the connection settings: https://github.com/porsager/postgres#connection-details

If you're using parameterized queries, then you _have_ to use PostgreSQL's "Extended Query" flow, which is what most people would think of as a "prepared statement". This is hardly opinionated. But normally, you use an unnamed prepared statement and/or portal, which PG will clean up for you, essentially only letting you have one of those per session (what we think of as a connection). I agree that sentence didn't make any sense. So I looked at the code (1) and what they mean is that they'll use a named prepared statement automatically, essentially caching the prepared statement within PG and the driver itself. They create a signature for the statement. I agree, this is opinionated! (1) The main place where the parse/describe/bind/execute/sync data is created is, in my opinion, pretty bad code: https://github.com/porsager/postgres/blob/bf

There's a core client interface here: - https://www.postgresql.org/docs/current/client-interfaces.ht... On what makes it postgres.js faster, from author himself: > it seems Postgres.js is actually faster than, not only pg, but of any driver out-there - https://github.com/porsager/postgres/discussions/627 - https://porsager.github.io/imdbench/sql.html

This is an outdated take. The left-pad incident was 7 years ago, and newer mainstream packages are generally doing a better job curating dependencies. That said, it is true that the Node/JS world is primarily hype-driven by "thought leaders" and people seeking personal brand and clout. Go on JS/React Twitter and prepare to loudly groan at the self importance on display. There are good packages out there that try to do things in a sane way without wasting your time. Postgres.js [1] is one of them. [1] https://github.com/porsager/postgres

there's also https://kysely.dev/ but personally i handwrite my queries with https://github.com/porsager/postgres for flexibility and performance most orms use node-pg lib which has shit performance.

When viewed as a DSL for set theory, views, CTEs, set-returning functions, et al are indeed proper first-class query abstractions. When viewed through the lens of general purpose imperative or functional programming languages, it's easy to see how it can be seen as falling short. I'll admit much of the tooling and driver APIs leave a lot to be desired. Some tools do make good efforts though such as nested fragments in this driver. https://github.com/porsager/postgres#building-queries

I don't think this should turn in to an ORM or not debate, but there are plenty of reasons, especially for the crowd that would do anything to avoid ORMs. Just try to take a peek into the multitude of "ORMs are bad" articles / discussions. For instance - I would love to be able to use https://github.com/porsager/postgres with sqlite.

Demonstrate how easily and accidentally one can make an SQL injection with these: https://github.com/porsager/postgres https://github.com/gajus/slonik

Agreed! First time I used the postgres Node library [0], I was sold! [0] https://github.com/porsager/postgres

I recently discovered https://github.com/porsager/postgres I think this is how an ORM for SQL databases should be. Unfortunately I don't use Node on the backend (Rails, Django, Phoenix) but I wish there would be ORMs like that for those frameworks. TLDR: write SQL with interpolated parameters, get the results parsed into objects.

In NodeJS land this library is pretty close to this: https://github.com/porsager/postgres