I want to use this as a chance to bring attention to a GitHub issue that I think would help reduce friction for Neon: https://github.com/neondatabase/neon/issues/4989. Having run a local dev environment connected to Neon and tests connected to Neon got in our way of adoption. We'd prefer to develop and run tests against a regular Postgres localhost database. To the PMs of Neon, put yourself in the shoes of a new... - Source: Hacker News / 2 months ago

I'd push you to consider using postgres, slonik or similar for database queries. With these libraries, you just write SQL, but they perform input sanitization for you. So you can safely write:. Source: 7 months ago

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. - Source: Hacker News / 9 months ago

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... - Source: Hacker News / 10 months ago

Demonstrate how easily and accidentally one can make an SQL injection with these: https://github.com/porsager/postgres. - Source: Hacker News / about 1 year ago

Traditionally, building business processes involves a highly database-centric approach. Development typically begins with a comprehensive database design, setting up schemas and tables before moving on to create classes and properties. These classes would then map to the database schema using Object-Relational Mappers (ORMs) like Entity Framework, NHibernate or Dapper. This method, while effective, often leads to... - Source: dev.to / about 2 months ago