GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — sqlite3: expect a generated column loop at CREATE TABLE by signfff · Pull Request #1373 · sqlancer/sqlancer

Conversation

@signfff

@signfff signfff commented Oct 20, 2026

Copy link
Copy Markdown

Fixes #1369.

A CREATE TABLE whose generated columns depend on each other has failed immediately with generated column loop on "..." since SQLite 3.44.0 (check-in af527231c), but SQLite3TableGenerator.createTableStatement did not list that message among its expected errors, so SQLancer raised an AssertionError and lost the thread — a false alarm on SQLancer's side.

This PR:

  • adds generated column loop to the expected errors of createTableStatement;
  • keeps SQLite3Provider.checkTablesForGeneratedColumnLoops for pre-3.44 SQLite, where the table is created and the loop only surfaces on first use;
  • adds TestSQLite3GeneratedColumnLoop, which replays the statement from the 2026-10-05 run that triggered this; the test fails without the fix and passes with it.

@mrigger as discussed in the issue.

🤖 Generated with Claude Code

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
signfff @claude
sqlite3: expect a generated column loop at CREATE TABLE
7a4ef37 
Since SQLite 3.44.0 (check-in af527231c, 2023-10-13) a CREATE TABLE whose
generated columns depend on each other fails at once; before, the table
was created and the loop surfaced on first use, which is the only place
SQLite3Provider.checkTablesForGeneratedColumnLoops expects it. Generated
columns are on by default since upstream sqlancer#1238 (2025-06), so the table
generator could hit an AssertionError on any current sqlite-jdbc: the
2026-10-05 trunk run lost a thread to it. The new test fails without the
change on that run's statement.

Co-Authored-By: Claude Code <[email protected]>
@signfff signfff mentioned this pull request Oct 20, 2026
SQLite: AssertionError on CREATE TABLE with a generated column loop (SQLite ≥ 3.44) #1369
Open
signfff
Merge remote-tracking branch 'origin/main' into generated-column-loop
9c6cae3
@signfff

signfff commented Oct 23, 2026

Copy link
Copy Markdown
Author

CI note: the three failing jobs (Citus, Presto, TiDB QPG) are pre-existing flakiness unrelated to this PR — the same jobs fail on main's own runs with the same signature (expected: <0> but was: <-1> after ~301s; the dockerized DB never becomes ready in time). E.g. run 39349907567 (2026-10-20) on main failed TiDB + Citus + SQLite, and 39349289518 (2026-10-20) failed TiDB + DataFusion + YugabyteDB. The SQLite job passes here.

I merged the latest main and pushed; the new run (39973562773) is waiting for workflow approval. @mrigger
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

SQLite: AssertionError on CREATE TABLE with a generated column loop (SQLite ≥ 3.44)

Uh oh!

There was an error while loading. Please reload this page.

1 participant

@signfff
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.