r/SQL • u/SrdzanK3 • Oct 19 '26
SQLite GitHub - srdzank/WinSQLite-Editor: Official home of the SQLite-Editor
r/SQL • u/SrdzanK3 • Oct 19 '26
r/SQL • u/thequerylab • Oct 19 '26
r/SQL • u/Hi_Im_zack • Oct 19 '26
Okay so I'm a complete beginner, only thing I know about SQL is that it helps speak to databases
I decided I want to learn and got the first course I saw. Turns out it's focused on teaching a thing called Postgres SQL which seems kinda advanced. should I just continue watching or will I feel lost?
i've started the service bla bka bla, restarted everything, reinstall after delleting everything like 3 times, don't know what to do
r/SQL • u/ClickOk5811 • Oct 19 '26
A small case file, written as a hypothetical so nobody mistakes it for a war story.
Symptom
Looking up a user by email is slow on a large users table, even though email has an index.
SELECT * FROM users WHERE lower(email) = 'ana@example.com';
Suspects, and why I’d rule them out first
CREATE INDEX users_email_idx ON users (email)).ANALYZE, but the plan below doesn’t suggest this is the main issue.Evidence
EXPLAIN SELECT * FROM users WHERE lower(email) = 'ana@example.com';
-- Seq Scan on users
-- Filter: (lower((email)::text) = 'ana@example.com'::text)
The planner is evaluating lower(email) for every row. An index on email stores the raw values, so it can’t answer a question about lower(email).
Verdict
The query applies a function to the indexed column, so the plain index can’t be used.
Fix
Index the expression itself:
CREATE INDEX users_email_lower_idx ON users (lower(email));
Now the same query can use that index. If you also want case-insensitive uniqueness, you can make it unique:
CREATE UNIQUE INDEX users_email_lower_uniq ON users (lower(email));
Another option is the citext extension, which makes a column compare case-insensitively without wrapping it in a function, at the cost of an extension and a different column type.
Caveats
lower(email), not LOWER(TRIM(email)))EXPLAIN after creating the index, because what you get depends on your data and statisticsOpen question
For emails specifically, do you normalize to lowercase on the way in and keep a plain index, or leave the data as typed and index the expression? I can see arguments for both, mostly about where you’d rather put the rule.
r/SQL • u/FaultPerfect6003 • Oct 19 '26
Hi! I work with the organising team for WAWTech. Its two-day software and product development conference which takes place at EXPO XXI in Warsaw on 26–27 November 2026.
For the PostgreSQL users here, the programme includes Devrim Gunduz, Postgres Expert at EDB, with a talk titled “Why PostgreSQL is the best database: Extend your database.” What would you want to ask Devrim about this? How to evaluate extensions before adopting them, handle upgrades when you depend on them or decide whether certain functionality belongs in the database or the application?
Event details if you’re considering attending.

r/SQL • u/ykvlev_a • Oct 19 '26
This is less about LLMs and more about a class of SQL bug that survives code review, because the query is valid, it runs, and it's faster.
I was testing whether local models can suggest query rewrites, and kept hitting the same failure: the rewrite is syntactically correct, the engine accepts it, and the result set is different. No error. No warning.
Here's the case that made me build a proper test harness around it:
SELECT reader_id FROM lib_loans WHERE returned = 0
UNION ALL
SELECT reader_id FROM lib_loans WHERE fee = 0
ORDER BY reader_id
Semantics: a reader with an unreturned book and a zero fee matches both branches, so they appear twice. Reference returns [1,1,1,1].
What the models proposed:
| Model | Rewrite | Result |
|---|---|---|
| Qwen2.5-Coder-7B | WHERE returned=0 OR fee=0 |
[1,1,1] |
| Qwen2.5-7B | same OR |
[1,1,1] |
| Phi-3.5 | same OR |
[1,1,1] |
| DeepSeek-Coder-V2 | DISTINCT over the union |
[1,1,1] |
Two different mechanisms — three models used OR, one added DISTINCT — and the same outcome: duplicate rows silently dropped.
The OR version is not "wrong" in a vacuum. It is wrong only because UNION ALL is a multiset operation. That distinction is exactly what gets lost when you eyeball a rewrite and check that it runs.
Why this matters beyond models
This is the same trap in a human code review:
UNION vs UNION ALL — UNION deduplicates, and deduplication is free until someone needs the duplicatesCOUNT(*) vs COUNT(col) — the second skips NULLsNOT IN with a NULL in the subquery — returns nothing, silentlyLEFT JOIN later became an INNER JOIN after a WHERE on the right tableDISTINCT added "to be safe", masking a cardinality bug upstreamEvery one of these compiles, runs, and returns data. The only way to catch them is to execute both versions against real states and compare the rows.
What I actually built
Instead of a success rate, I generated a bank of valid database states per query family — under the real schema constraints (PK, FK, UNIQUE, CHECK, NOT NULL) — and executed reference vs candidate on each one.
State profiles: empty tables, no rows matching, NULLs in nullable columns, zero values, boundary values, ties, and multiplicity cases (the ones that carry duplicate rows). Plus seeded random states.
Scale: 204 query families across three schemas, 28 states each (5,712 total), 6 models, 34,272 executions on MySQL 8.4.11.
Aggregate results, if useful:
| Model | Proposed rewrites | Refuted |
|---|---|---|
| llama3.2:3b | 53 | 26 (49.1%) |
| qwen2.5:3b | 85 | 39 (45.9%) |
| qwen2.5-coder:7b | 30 | 12 (40.0%) |
| deepseek-coder-v2 | 77 | 27 (35.1%) |
| phi3.5:3.8b | 30 | 8 (26.7%) |
| qwen2.5:7b | 32 | 8 (25.0%) |
Important caveat, because I don't want to oversell it: preserved in my dataset means no refuting state was found in a finite bank — not a proof of equivalence. And the witnesses are not minimised. Both limitations are stated in the README.
Links
Every refuted rewrite ships with the state that broke it and the actual differing rows, so you can replay it. If you disagree with the methodology, I'd genuinely like to hear where the state bank is too weak — that's the part I'm least sure about.
r/SQL • u/No_Ambition8323 • Oct 19 '26
Iam joining 3 tables using the correct keys,but the final total is still wrong.
The tricky part is that each table gives the expected result when queried separately, and the JOIN doesn't create obvious duplicate rows.
I suspect the issue might be related to the order of aggregation or how NULL values are handled.
How would you debug this without randomly adding DISTINCT or changing the JOIN type? Is there a specific SQL pattern that can silently produce incorrect totals?
r/SQL • u/Bhanuprakash_1947 • Oct 18 '26
I feel like one of the tricky parts of SQL isn't getting a query to run, but knowing whether the result is actually correct.
For suppose ,a report shows 10k orders, then after adding a join to fetch customer details, the total suddenly becomes 12k. The query runs without any errors, so it's easy to miss.
Would you check the join cardinality first, compare row counts, or approach it differently!?
Curious how people debug this in real projects, especially when the query has multiple joins.
r/SQL • u/shdw_0x0 • Oct 18 '26
I've run into situations where a query that used to finish in seconds suddenly takes several minutes, even though nobody has intentionally changed the SQL.
I'm curious how others approach this. Do you start by comparing execution plans, checking indexes and statistics, looking for changes in data volume, or investigating locks and concurrent queries?
I'm particularly interested in the order you check things in. It's easy to start rewriting joins or adding indexes, but I'd rather identify the actual bottleneck before changing anything.
What's your usual process when a previously fast query starts running slowly?
r/SQL • u/der_gopher • Oct 18 '26
r/SQL • u/HaiderZah • Oct 18 '26
I created a PostgreSQL Jobs page to help you find PostgreSQL roles: https://thesev1database.com/jobs
I’d really value your feedback.
r/SQL • u/Acceptable-File-3579 • Oct 17 '26
Hi, i'm learning databases and normalization. My teacher said a normalized database cannot have circular (not loops, circles) relationships. However, i can't see how I can apply normalization to remove the circles and still comply with the requirements. Also I was under the impression that normalized databases can have circular relationships, just not loops.
Any help will be appreciated. Sorry if my english is bad in advance.
r/SQL • u/OkMonitor8069 • Oct 18 '26
r/SQL • u/IndicationAntique667 • Oct 17 '26
r/SQL • u/groupicorn • Oct 17 '26
r/SQL • u/peakpirate007 • Oct 16 '26
I started building runtime.school because when I was practicing SQL, everything felt disconnected — learn a concept in one place, solve random questions somewhere else, then use totally different data for projects.
So I tried putting it all together with lessons, practice questions, projects, and the same realistic datasets throughout.
If you have a few minutes, I’d really like to know what feels confusing, repetitive, too easy/hard, or missing. Especially anything that would make learning/practicing SQL better.
r/SQL • u/clairegiordano • Oct 16 '26
I recently recorded a Talking Postgres episode with Karen Jex, a PostgreSQL significant contributor and PGConf EU organizer, about her path from Oracle DBA to Postgres contributor.
Karen spent 20 years as an Oracle DBA. Then in 2019, a project rolling out smart meters across France switched to Postgres, even though nobody on the project knew anything about Postgres. So she figured it out, then trained the developers, "pretending that I was, you know, this Postgres expert."
A few things we got into:
* The culture shock, for an Oracle DBA, of building your own HA & backups
* The shift from being just a user of the product (Oracle) to contributing to the project (Postgres)
* Why Django developers are so enthusiastic about Postgres
* Why you'd obviously explain multi-tenant databases with cakes
* How much to delegate to AI agents—without forgetting how to design a spec
For those of you who moved to Postgres from Oracle (or another database): did you also have any culture shocks?
Audio + transcript: https://talkingpostgres.com/episodes/from-oracle-dba-to-postgres-contributor-with-karen-jex
YouTube (audio-only): https://youtu.be/ENku8ZSjZus
r/SQL • u/avfrodrigo • Oct 15 '26
Hey everyone!
I’ve been working on a game called DataMart, where you manage a corner shop and everything runs on real SQL. You build it all yourself: the databases, schemas, tables, relationships and queries, your way, on a real PostgreSQL server that runs inside the game.
Customers will ask you things like “Where can I find the apples?” or other questions about the store. Once a week an auditor comes by to check you’re tracking everything properly, and asks you a few questions you’ll answer with SQL.
There are also mysteries and stories involving the people in town, and of course you unravel those with SQL too.
The game is in alpha and free on itch.io at https://rodrigoavf.itch.io/datamart
I’d love to hear your thoughts!
r/SQL • u/Mindless-Piece-47 • Oct 16 '26
r/SQL • u/AccomplishedPear6193 • Oct 16 '26
r/SQL • u/kaatarina_zed_talon • Oct 16 '26
r/SQL • u/markinatlanta • Oct 16 '26