Travis Athougies

Oh I see. So what's happening here: `runMigrationSilenced` produces a `CheckedDatabaseSettings` which is an object that can be used to *check* that a database schema matches your own, but which...

Sorry for the confusion here. `beam-migrate` has a lot of type conversion functions and many are lossy.

Did you try with `bringUpToDate`?

The reason this hangs is because beam-migrate currently implements a graph search algorithm. It currently retraverses paths that are the same, but due to the way the traversal is structured...

It'll terminate eventually, but it's incredibly inefficient yes. Usually, in the event that it doesn't terminate quickly, the eventual result is going to be that it could not find any...

Are you running this on postgres, or something else? What's the SQL type for Foo_BarQualifier? That's probably where it's getting hung up.

BTW, The predicates for a valid solution are mainly in http://hackage.haskell.org/package/beam-migrate-0.4.0.1/docs/Database-Beam-Migrate-Actions.html Beam-postgres has a few more, but you don't seem to be doing anything postgres-specific here. I will investigate.

> I suppose the solver was overwriting values of tables / tables and columns after applied some naming rule? Oh my... yes you're right, and I can't believe I didn't...

`beam-sqlite` re-uses the parsers from sqlite-simple. My suggestion for this particular use case, since this is ultimately a non-standard format for dates, is to define ``` newtype MyTime = MyTime...

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