The “Select Everything” Trap in n8n
- Feb 13
- 1 min read
What this means (non-technical)
Using SELECT * in a database query retrieves every column from a table. This includes fields you may not need, such as large text or JSON columns.
It makes the workflow handle more data than necessary.
What usually goes wrong
When unnecessary columns are fetched:
Memory usage increases.
Network transfer time grows.
Processing downstream nodes becomes slower.
Changes to the database schema affect your workflow unexpectedly.
If the table contains large fields, performance can degrade quickly.
The workflow may slow down even though you only needed a few simple columns.
When this becomes urgent
This becomes urgent when:
Tables contain large text, JSON, or binary fields.
You fetch many rows at once.
Memory usage increases unexpectedly.
Database performance declines.
The more data returned, the more resources are consumed.
Detect issues in your n8n workflows
|
Definitions
SELECT *: A SQL statement that retrieves all columns from a table.
Schema: The structure of a database table, including its columns.
Disclaimer
This article highlights common patterns and risks seen in real-world n8n workflows. It’s meant to help you build more confidently and avoid surprises as your automation grows. Behavior can vary depending on your setup, version, and configuration.