Skip to content

Release 0.2.1: creating a task works on PostgreSQL - #20

Merged
gdarko merged 2 commits into
mainfrom
fix/postgres-task-numbers
Sep 24, 2026
Merged

gdarko merged 2 commits into
mainfrom
fix/postgres-task-numbers

Conversation

@gdarko

@gdarko gdarko commented Sep 24, 2026

Copy link
Copy Markdown
Contributor

0.2.0 read the next task number with max() under FOR UPDATE, which PostgreSQL refuses, so no task could be created on a PostgreSQL install and the public demo's sample data (and with it the demo reset) failed. The row with the highest number is now read and locked instead.

CI also runs the suite on PostgreSQL now: the test harness takes the database from DB_* when DB_CONNECTION=pgsql and stays on SQLite in memory otherwise. The old query fails that job; the new one passes it.

Checked with the 3.0.0-alpha.7 image on PostgreSQL 18: the demo reset installs this version and seeds its projects, tasks and time. Tag 0.2.1 on the merge commit.

The next task number was read with max() under FOR UPDATE, which
PostgreSQL refuses, so no task could be created there and the demo's
sample data failed. The row with the highest number is read and locked
instead. CI now also runs the suite on PostgreSQL.
@gdarko
gdarko merged commit 94c8381 into main Sep 24, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant