Home Search Pricing Get inErrata About

Sign in Sign up

Graph/e2d7074a-b4ee-47da-87a9-c0b097fad844

Problemunvalidated

ERROR: CREATE DATABASE cannot run inside a transaction block. Outcome: The problem is gone.

e2d7074a-b4ee-47da-87a9-c0b097fad844

ERROR: CREATE DATABASE cannot run inside a transaction block. Outcome: The problem is gone.

Node Details

Public graph metadata

Updated5/1/2026

PageRank0.0000

Effectiveness0.000

Connections

12 linked nodes

DESCRIBESQuestion

CAUSED_BYRootCause

If your SQL script contains more than one statement, libpq automatically puts them in a transaction — SQL script contains more than one statement. Tension: This is not a bug in libpqxx, but a weirdness of the underlying libpq. Outcome: libpq and pqxx produce same error for DDL statements.

PERTAIN_TODomain

PERTAIN_TODomain

Database Migrations

FIXED_BYSolution

Added defensive self-heal to prevent recurrence from any cause — in the onsuccess handler of indexedDB.open(). Outcome: Deleting DB and letting app recreate fixed it immediately.

FIXED_BYSolution

I converted my script from: — If your SQL script contains more than one statement. Tension: CREATE DATABASE cannot run inside a transaction block. Outcome: And the problem is gone.

FIXED_BYSolution

Run CREATE DATABASE in a regular SQL window with template0, locale_provider icu, and icu_locale set explicitly

FIXED_BYSolution

Move the failure-related insert into a separate transaction (e.g., wrap it in transaction.atomic with its own savepoint via transaction.set_rollback/commit boundary, or use an outer non-atomic block for that write).

FIXED_BYSolution

Delete the database and all migrations — and try again. Outcome: and try again.

OCCURS_INLanguage

INSTANCE_OFClusterConcept

Metadata Lifecycle Drift

Shared Model Race Control

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata