pgadmin4 VS Knex

If we access a client like PgAdmin or Beekeeper, or accessing its container via bash and checking via CLI, we can see that the table was created successfully:

You can install pgAdmin on Windows and connect the GUI Admin/developer tool directly to your PostgreSQL server running in WSL.

With this tool, deciphering the details of PostgreSQL query plans becomes a little more approachable. Just be mindful that using it involves sharing your query and its plan publicly. If privacy is a concern regarding sharing your query and its plan publicly, consider using pgAdmin, an open-source administrative tool for PostgreSQL that you can install on your local machine, which also offers a visualization feature for query plans.

This isn’t meant to be an exhaustive list. There are many other database management software packages out there, including MySQL Workbench, DBeaver, and pgAdmin. We’ve chosen these database tools because they cover the most common database systems and use cases, but if you find they aren’t meeting your needs, be sure to explore further or consider building your own database user interface — it’s easier than you think.

pgAdmin to PostgreSQL is what phpMyAdmin is to MySQL, and it can be used on Linux, Unix, macOS and Windows to manage PostgreSQL. pgAdmin 4, the latest pgAdmin, is a complete rewrite of pgAdmin using Python and Javascript/jQuery.

I've attached my full crash report. Please, HALP! I don't want to keep using DBeaver! crashreport-jont.pdf

Knex.js

AdonisJS core team has created/maintains Lucid. It is a SQL query builder, and an Active Record ORM built on top of Knex.

Now, why not use an ORM? I've seen performance issues too many times with ORMs. I prefer writing my own SQL to avoid surprises. After all, I know the database schema and writing code for a specific purpose very often leads to better performance than generic code. ORMs have to support all kinds of database schemas. I only have to support mine. Having successfully used Knex.js in NodeJS (a popular query builder) in the past, I know writing SQL queries myself is not hard and provides very good performance.

Given the dynamic nature of the schema, we employ Knex, a query builder, for database access.

https://www.npmjs.com/package/knex - 779 issues

# related: https://github.com/knex/knex/issues/2354

This article will be focused on a security issue that I found in Knex and how to mitigate it, but I'll also talk briefly about the social aspects of this problem.

SQL is an old, irregular language to work with, but it is better known than HCL and SQL already has it's own Pulumi/CDK in the form of every ORM with introspection (like Javascript's Prisma, Python's Django, Go's XO etc) and QueryBuilder (LINQ, Knex, etc) in whatever programming language you prefer. You probably already know it.