Repository navigation
Define postresql schema update strategy #901
Description
In #731 we added a PostgreSQL based backend to replace ValKey. We need to define how Substrate will keep track of DDL commands to evolve the SQL schema, and the machinery to run / apply the schema changes during upgrades in a reliable way.
Reacted by Jonathan Jamroga
Activity
EItanya commentedon Aug 19, 2026
Jeremy Alvis (@iplay88keys) assigning you.
It won't let me officially do it...
iplay88keys commentedon Aug 21, 2026
Edit: The proposal doc is now at: https://docs.google.com/document/d/13ixDKRoAIFXeLxS-_1nikNcAy76ca8m0eVgobfib93E/edit?usp=sharing (need to be part of the ate-dev@googlegroups.com google group to access)
maxsmythe commentedon Aug 22, 2026
I'm in ate-dev, but no access?
iplay88keys commentedon Aug 24, 2026
Max Smythe (@maxsmythe) I'm looking into this. It seems like an org-level sharing policy that I don't have visibility into. I'm working with my IT team to resolve it. Can you request access in the meantime?
iplay88keys commentedon Aug 25, 2026
I have a PR up for this here: #1196
iplay88keys commentedon Aug 25, 2026
Julian Gutierrez Oschmann (@juli4n) Max Smythe (@maxsmythe) In order to resolve the share permissions, I had to move the doc. The new link is here.
ateapi: add versioned PostgreSQL schema migrations (agent-substrate#1196