beam-automigrate

beam-automigrate copied to clipboard

In the case of a default column constraint being set on a `timestamp with time zone` column, the comparison between the value as reported to beam-automigrate by postgres and the...

cgibbard

In the case that a diff indicates that a column constraint has been both added and deleted (in particular when a default constraint changes), the migration first adds the new...

cgibbard

Use system catalogs instead of 'information_schema'

1

ymeister

cgibbard

Fixes issue #16. Gargoyle only appears to be used in the README executable stanza. Haskell build tools tend to treat executable stanzas as belonging to the project, so it seems...

mightybyte

More robust constraint/sequence diffing.

2

This PR hopefully improves beam-automigration hadnling of most types of constraint, and in how it handles sequences; so that they can be used in more cases and with fewer surprises....

danbornside

[x] Plan migration in the same transaction as the attempted execution [x] Expose attempted migration without transaction so user can embed it in their own [] unmangle the haddocks []...

madeline-os

Add safety-checking hook to 'tryRunMigrationsWithEditUpdate'

2

alexfmpe

Change foreign key constraint names (#38)

4

This changes foreign key constraint names to be based on the table and columns of the foreign key, so that they are unique. This is a breaking change. See #38...

TravisCardwell

Currently, [`TableConstrint`](https://github.com/obsidiansystems/beam-automigrate/blob/6e1f316576d8ad0b9a91f691059d67952e51c648/src/Database/Beam/AutoMigrate/Types.hs#L183-L191) columns are stored using `Set`, so the order is determined by `Set.toList`. ```haskell data TableConstraint = PrimaryKey ConstraintName (Set ColumnName) | ForeignKey ConstraintName TableName (Set (ColumnName, ColumnName)) ReferenceAction...

TravisCardwell