Carlos Pérez-Aradros Herce

Thank you for your feedback! This is indeed something we want to tackle soon, as it's an important limitation. Now that we have all the foundations in place it feels...

Thank you for reporting! I gave this a try and to me, this is a bug. We need an `up` function in order to backfill values for the column, but...

Thank you for opening this issue! it could be nice to support other formats like YAML. My only concern would be around portability, having a common format for everyone makes...

Thank you for opening this! Support for partial indexes is indeed still pending. For now the alternative would be to use the sql migration to create them on your own,...

> So is the MAM problem can of worms worth solving now, or should this issue focus solely on bootstrapping? Having fewer or no exclusive operations like `sql` and `add_index`...

aah, good catch! a couple of things that come to mind you could try: * Adding `public` to the search path so the constraint is found: `SET search_path= public_my_migration,public;` *...

I would scope this issue to strictly validating the JSON against the spec. In the future we could improve this by: * Checking the migration is valid against the current...

Thank you for opening this one @ericwooley! We recently discussed this, and this is a possible approach we could take: * Migration files must be in a well-known (configurable) folder,...

I'm closing this for now as I believe no further action is planned / required, feel free to reopen if that's not the case!

this is entirely on me 🙏 , but I agree `not_null` is much better! btw, to do this backward compatible we could allow both `nullable` and `not_null` (but not both...