AA-morganhoke
PGRoll constraints not visible in latest migration
I've created an issue on the pgroll github here:
https://github.com/xataio/pgroll/issues/363
5 replies
Actually Cockroach doesn't support this
My current pain points are:
1. Because operations in a migration can't depend on each other (i.e. can't create a table and an index in the same migration) I'm ending up with tons of migrations to add new features, which sort of breaks the backwards compatibility of the schema. I think this is largely a point-in-time thing since this is a greenfield app and I'm making huge changes that I expect to slow over time, but I could see this being annoying long-term.
2. Some feature in Postgres that don't seem to have out of the box support:
- Multi column constraints
-- Worked around by using a sql migration, would much prefer a built-in
- Foreign key ON DELETE CASCADE
-- I don't want to have to write indexes in raw sql when there's already a built-in for handling foreign keys. It would be really nice for right-to-be-forgotten requests to be able to delete all data by a specific unique ID automatically.
4 replies
Actually Cockroach doesn't support this
Hi, since I wrote this I've been on a bit of a journey here lol.
CockroachDB has weird limits around what kinds and how many changes to schema (ALTER statements) it allows in a single transaction. I ended up dropping pgroll because it wasn't clear to me that it would necessarily play nice under cockroach's constraints.
Then we ended up switching to Aurora Postgres anyway, so I brought pgroll back. I've been really liking it but I'm starting to butt up against some limitations again.
4 replies