v0.6.40

v0.6.40 — the graph-id sequence follows the storage owner; every release gated on an upgrade from the previous one

Fixed

• No graph could be created after the 0.6.39 upgrade in databases where pgRDF's tables had been handed to another role (#153). Graph creation allocates ids from _pgrdf_graph_id_seq as the storage owner (the owner of _pgrdf_quads); the 0.6.39 upgrade created that sequence owned by whoever ran ALTER EXTENSION pgrdf UPDATE, so every new graph failed 42501 on nextval. Granting USAGE is not enough. The upgrade now gives the sequence to the storage owner. Fresh installs were never affected. When the storage owner cannot use the sequence, graph creation refuses 55000 with HINT ALTER SEQUENCE pgrdf._pgrdf_graph_id_seq OWNER TO <storage owner> instead of a bare permission error.

Added

• ownership_drift(): each storage relation not owned by the owner of _pgrdf_quads, whether it blocks pgRDF, and the ALTER … OWNER TO that realigns it. Empty when ownership agrees.
• CI upgrade gate: installs the previous release's SQL from its published, checksummed package, hands the tables to another role, upgrades, and checks graph creation, existing digests and parity with a fresh install. Red on 0.6.39, green on 0.6.40.

Upgrade

• ALTER EXTENSION pgrdf UPDATE in place; from 0.6.34–0.6.38 go straight to 0.6.40. surface() lists 54 stable rows. SHACL capability (47/47 enforced) and path matrix (17 cells, 0 defective) unchanged.

What's Changed

• 0.6.40: the graph-id sequence follows the storage owner; upgrade gate in CI by @styk-tv in #154

Full Changelog: v0.6.39...v0.6.40