Marcelo Zabani

We can maybe simplify this further and ask for migrations in pairs. Following our example of adding a column and indexing it concurrently, the migration that adds the column is...

I am not able to reproduce the issue with whitespace in functions. I created this function: ```sql CREATE FUNCTION test_function_with_whitespace() RETURNS INT AS $$ BEGIN SELECT 1; -- White space...

> I am currently using PostgreSQL 11, which has the problematic behavior that I described. I see. I'll try to find the most recent version of postgres where this still...

> Hmmm, I do not foresee too many options, but perhaps I am being naïve. I ran into a curious case this week at work, where I could conceivably want...

I forgot to mention, codd has a provision for when it _errors out_ parsing SQL: you can add `-- codd: no-parse` to the top of your migrations (the parser will...

I have pushed a draft to ensure that pg_dump -> restore is an identity wrt codd schemas, and the test function with empty spaces is there and passes, even with...

I merged the PR with the pg_dump + restore = identity test given the utility of such a test, but I'm not marking this as fixed until we get to...

I'm taking the liberty of closing this issue for a few reasons: - There is https://github.com/mzabani/codd/issues/167 with a solution to the problem of relaxing consistency equality checks, and it solves...

This problem has further complications. Suppose an app is deployed very frequently. Say the app is deployed and its multiple instances of _codd_ are waiting on each other or even...

While working on this I realised that because codd allows resuming failed no-txn migrations from the last failed statement, we would need to store the value of `standard_conforming_strings` in codd's...