Overcoming non-implemented parts of beam-migrate

[GulinSS]

It is known that beam-migrate has some gaps in DDL implementation. For example this one: #502

But these features are important and due of complexity level of beam design it is hard to participate development as a contributor.

Starting this thread is an attempt of discussion to collect ways of workarounds how we can overcome missed DDL-related stuff while beam core developers are busy with other things.

[GulinSS]

My first attempt regarding missed constraints: #502 (comment)

[kmicklas]

With the current feature set, I personally don't recommend using beam-migrate for migrations. In my own projects I only use it for checking that the schema in code matches the live schema (which it works fine for), and I just write DDL scripts by hand.

That said, I do really wish we supported the common migration features that are missing. I don't believe there is any technical reason they can't be added.

If there is a specific feature you need, and you have time to dig into the code, I highly recommend just going ahead and trying to implement it. This is @tathougies's project originally but I just started submitting PRs for things I needed while using Beam and now I am a maintainer. 😂

Unfortunately, I don't really have the time these days to implement feature requests from the community, but I do try to keep up with PRs and I'm happy to answer any questions about design or to give code pointers if something isn't clear.

[tathougies]

I am very happy to guide people on how to implement things! As Ken said, he got roped in by submitting MRs :)