A tied ORDER BY still leaves part of the order unspecified
A stable list needs a final ordering key that distinguishes otherwise equal rows.
Topic · 17 stories
17 stories tagged sql on AI Tamer, newest first.
A stable list needs a final ordering key that distinguishes otherwise equal rows.
Combining two result sets needs a decision about whether repeated values represent repeated events.
DuckDB's team explains why storing data by column makes it fast. We tried the ideas on a small LLM eval log, with short queries you can run in a minute.
Rows with the same ordering key can share a cumulative result unless the frame says otherwise.
Explicit NULL ordering makes a ranked list easier to understand and maintain.
A dashboard count needs to say whether it measures records or populated fields.
A uniqueness rule on an optional field does not also require that field to be present.
Spice v2.4.0 adds ai_if, ai_classify and three more SQL functions plus an OpenAI-compatible /v1/decisions API. Cayenne is now the default accelerator.
A NOT IN query can lose every candidate when its exclusion set contains NULL. A small SQLite example shows why and how a correlated NOT EXISTS changes the result.
SQLite 3.54.0 is dated 9 October 2026, ahead of the 15 October date still on its draft changelog. The release overhauls the shell, drops Windows XP, and adds limits for untrusted SQL.
PostgreSQL accepts a CHECK expression that evaluates to NULL. Make optional positive quotas explicit, and pair CHECK with NOT NULL when a value is required.
Polars 2.0, published 6 October, enables an initial spill-to-disk path and treats SQL as first class. Its TPC-H and TPC-DS-derived times against named DuckDB and DataFusion builds are Polars' own runs.
Column order changes how much of a multicolumn B-tree index PostgreSQL must scan. Match the leading columns to the conditions in your queries.
SKIP LOCKED helps competing workers claim jobs without waiting. The same behavior can make an ordinary query silently omit rows it would otherwise find.
Use a PostgreSQL exclusion constraint to keep active reservations for the same GPU from overlapping. Range bounds and cancellation rules make the schedule explicit.
SQLite savepoints let you undo later work while keeping the surrounding transaction open. Here is how to use one and decide what to commit.
A partial index over pending jobs helps only when PostgreSQL can tell that the query asks for rows covered by the index.