Our great sponsors
pev2 | sqlc | |
---|---|---|
40 | 169 | |
2,363 | 10,950 | |
3.4% | 6.5% | |
7.7 | 9.6 | |
12 days ago | 3 days ago | |
TypeScript | Go | |
PostgreSQL License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pev2
-
Retrieving the latest row per group from PostgreSQL
This runs in about 250ms. Let's have a look at the explain plan to understand it better. To visualise it, I am using the excellent visualisation tool from Dalibo.
-
Pg_hint_plan: Force PostgreSQL to execute query plans how you want
The PEV2 is open source and give you a good visualization. I never used this pgmustard to compare.
https://explain.dalibo.com/
-
Efficient Database Queries in Rails: A Practical Approach
Visualize Your Plan: Visit explain.dalibo.com and paste the generated plan text and query. Then, hit Submit. The tool will generate a visualization of your query plan. Here's an example of the visualization for the fifth attempt version of the query from this post. It shows the different types of scans that were used and how the data gets combined. The duration of each operation is also shown:
-
What's new in the Postgres 16 query planner (a.k.a. optimizer)
You can download the whole analyzer as a simple html file and use it this way. No need to obfuscate or sanitize anything at all.
https://github.com/dalibo/pev2
- Visualizing and understanding PostgreSQL EXPLAIN plans made easy
- Don't use DISTINCT as a "join-fixer"
-
When should you use the IN instead of the OR operator in Postgres queries?
You might be interested in sites like https://explain.dalibo.com/ which make the output a bit nicer to read. I use these quite often to quickly identify bottlenecks.
-
200 Web-Based, Must-Try Web Design and Development Tools
PostgreSQL Query Plan Analyzer and Visualizer
-
Do you use pgAdmin? Why?
I didn’t know about pev2, interesting, checking it now. Did you integrate the component yourself or are you using this hosted page by them: https://explain.dalibo.com/?
-
Tuning DB
IMO it‘s important to get started with indexing. Grab your most frequently used queries and run an EXPLAIN ANALYZE to identify the problems. This tool might help you to understand your execution plans. Once you identified your problems, you can build indexes and check again. Then you should regularly check if your indexes are used.
sqlc
-
Give Up Sooner
"Is there a way to get sqlc to use pointers for nullable columns instead of the sql.Null types?"
-
Show HN: Sqlbind a Python library to compose raw SQL
I came across this yesterday for golang: https://sqlc.dev which is somewhat like what you want, maybe.
Not sure it allows you to parameterize table names but the basic idea is codegen from sql queries so you are working with go code (autocompletion etc).
- API completa em Golang - Parte 7
-
ORMs are nice but they are the wrong abstraction
Agreed, but tools like https://sqlc.dev, which I mention in the article, are a good trade-off that allows you to have verified, testable, SQL in your code.
- API completa em Golang - Parte 6
-
Go ORMs Compared
sqlc is not strictly a conventional ORM. It offers a unique approach by generating Go code from SQL queries. This allows developers to write SQL, which sqlc then converts into type-safe Go code, reducing the boilerplate significantly. It ensures that your queries are syntactically correct and type-safe. sqlc is ideal for those who prefer writing SQL and are looking for an efficient way to integrate it into a Go application.
-
Type-safe Data Access in Go using Prisma and sqlc
I was browsing awesome-go for ideas on how to setup my data access layer when I stumbled on sqlc. It seemed like a great option. Code generation is a strategy often used in the Go ecosystem and making my queries safe at compile time was an idea I really liked. Knex was great, but it required of me that I test thoroughly my queries at runtime and that I sanitize my query results to ensure type safety within my application.
-
Level UP your RDBMS Productivity in GO
Now, we are going to generate the code. For this purpose, we are going to use sqlc.
-
What 3rd-party libraries do you use often/all the time?
https://github.com/sqlc-dev/sqlc — for use with //go:generate
- API completa em Golang - Parte 1
What are some alternatives?
TypeORM - ORM for TypeScript and JavaScript. Supports MySQL, PostgreSQL, MariaDB, SQLite, MS SQL Server, Oracle, SAP Hana, WebSQL databases. Works in NodeJS, Browser, Ionic, Cordova and Electron platforms.
sqlx - general purpose extensions to golang's database/sql
awesome-db-tools - Everything that makes working with databases easier
GORM - The fantastic ORM library for Golang, aims to be developer friendly
hypopg - Hypothetical Indexes for PostgreSQL
SQLBoiler - Generate a Go ORM tailored to your database schema.
pev - Postgres Explain Visualizer
ent - An entity framework for Go
sysbench - Scriptable database and system performance benchmark
jet - Type safe SQL builder with code generation and automatic query result data mapping
yugabyte-db - YugabyteDB - the cloud native distributed SQL database for mission-critical applications.
pgx - PostgreSQL driver and toolkit for Go