Benchmarking LLM query generation across SQL, Cypher, and TypeQL
All PostsEngineeringProductUse CasesInsightsCommunityEngineeringBenchmarking LLM query generation across SQL, Cypher and TypeQLExplore our new LLM benchmark comparing MySQL, Neo4j, and TypeDB. Learn how context and retry budgets help AI agents self-correct and improve performance. Samuel ButcherSep 17, 2026 · 21 min read A report on the Claude Sonnet 5 / DeepSeek V4 Pro run of db-llm-bench Summary We ran a benchmark to test LLM query generation across multiple different database query languages.
- ▪All PostsEngineeringProductUse CasesInsightsCommunityEngineeringBenchmarking LLM query generation across SQL, Cypher and TypeQLExplore our new LLM benchmark comparing MySQL, Neo4j, and TypeDB.
- ▪Learn how context and retry budgets help AI agents self-correct and improve performance.
- ▪Samuel ButcherSep 17, 2026 · 21 min read A report on the Claude Sonnet 5 / DeepSeek V4 Pro run of db-llm-bench Summary We ran a benchmark to test LLM query generation across multiple different database query languages.
Hacker News (AI / LLM) files mainly under ai. We currently carry 6,119 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Hacker News (AI / LLM) |
| Canonical URL | https://typedb.com/blog/benchmarking-llm-query-generation-across-sql-cypher-and-typeql |
| Publication time | Wed, 23 Sep 2026 13:37:23 +0000 |
| Retrieval time | 2026-09-23T13:39:30.794Z |
| Last seen | 2026-09-23T13:39:30.794Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | u0NXH_m0UqAy · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
All PostsEngineeringProductUse CasesInsightsCommunityEngineeringBenchmarking LLM query generation across SQL, Cypher and TypeQLExplore our new LLM benchmark comparing MySQL, Neo4j, and TypeDB. Learn how context and retry budgets help AI agents self-correct and improve performance. Samuel ButcherSep 17, 2026 · 21 min read A report on the Claude Sonnet 5 / DeepSeek V4 Pro run of db-llm-bench Summary We ran a benchmark to test LLM query generation across multiple different database query languages. This benchmark attempts to understand, for a fixed task, what happens when you vary the LLM used, the database used, as well as information available in the prompt and how many times we allow a retry in the face of an error.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Hacker News (AI / LLM).
Discussion
0 commentsMore from Hacker News (AI / LLM)
