linkin VS postgres

Hi everyone , LinkIn is an open-source self-hosted link tree application‏‏‎‏‏‎‏‏‎‏‏‎­that you can customize to form your own link tree page. Visit Demo (`read-only`) to access admin visit http://linkindemo.vercel.app/admin * Demo username = admin * Demo password = linkin123 GitHub Repo FrontEnd - Next.js API - Next.js Serverless functions ORM - prisma Database - Postgres linkin supports external images via its URL, icons via font fontawesome, and fonts via an external font URL (google fonts). you can deploy your own linkin app with the one-click deploy button in the GitHub readme, and connect it with a Postgres database. I created this because of my friend, who owned an Instagram page. he needed a link tree. I created a plain HTML CSS link tree page first but then, whenever he needed to change data I need to change HTML and redeploy that. so I came up with linkin. you can edit page data, update links, and stuff. I am planning to add more features, and hoping to add simple analytics also in the future. Share your valued opinions and thoughts. Thanks for reading.

workflow file

GitHub Repo

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

If the Neon driver were to allow us to easily pass in a localhost connection, the development and test experience would be easier. Perhaps Neon could swap to something like this internally: https://github.com/porsager/postgres.

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 developer thinking of giving Neon a try. What changes will I have to make to my code and my development workflow?

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:

Thanks Pier! Your comment saved me some frustration here :-D

https://github.com/porsager/postgres/discussions/627#discuss...

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

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

They've looked at Postgres.js (https://github.com/porsager/postgres) before — wouldn't mind if they enabled those other cases in the same way.