Dragon ze 9a92d2e9b7

fix(persistence): treat a peer's database creation as success (#7489) ...

Two Gateways booting the same missing database both reach CREATE DATABASE and
only one wins; the loser aborted startup with duplicate_database (42P04) even
though the winner's catalog row was already committed and the target was
usable. Follow the SQLSTATE, like the missing-database check beside it does, so
the loser falls through to its retry. Every other failure -- permission denied
included -- still propagates untouched.

2026-10-25 23:00:40 +08:00

..

extension-api

feat(workflows): add multi-Gateway coordination and session-authorized failover (#7138)

2026-10-23 23:31:43 +08:00

harness

fix(persistence): treat a peer's database creation as success (#7489)

2026-10-25 23:00:40 +08:00