Travis Cardwell

I wrote [my thoughts about migration][] for this issue. [my thoughts about migration]: As noted in the [solution][] section for this issue, this change does not fix the issues with...

I have run into constraint name length issues in my project as well. Since foreign key column names are prefixed with the table name when using Beam naming conventions, the...

By the way, this is my second of a series of pull requests. I am submitting them sequentially so that each one can be trivially merged, with no merge conflicts,...

I created a [`tc-develop`][] branch with documentation in the [`README-tc-develop.md`][] file. The plan is to separate commits with actual changes from documentation commits, so that they can be cherry-picked, and...

A [`GTableConstraintColumns` instance](https://github.com/obsidiansystems/beam-automigrate/blob/6e1f316576d8ad0b9a91f691059d67952e51c648/src/Database/Beam/AutoMigrate/Generic.hs#L339-L366) is used to create the foreign key constraint annotations when automatic foreign key discovery is used. The constraint names are already based on the table and columns...

I wrote: > I can create pull request branches with cherry-picked commits and label them with the order. That did not work well, as the new pull request seems to...

FYI: I am currently working on a checkpoint migration, and I hacked some options into the `codd verify-schema` command. The code is pushed to the [`verify-schema-options`][] branch of the [`BeFunctional/codd`][]...

> I am not able to reproduce the issue with whitespace in functions. Interesting! I confirmed this using PostgreSQL 15.2, and I am happy to see that this was changed!...

> Ah, interesting! I wonder if we can think of some sensible code-like structure that specifies how things should be compared? I fear the proliferation of options. Although.. having some...