Eitan Chatav
Eitan Chatav
interesting...clearly GHC's having trouble inferring `field1` and `field2`. It should be able to infer them from the `HasAll` constraint but it can't because it's not fully applying the type families...
You can still decompose monomorphically though. In my project I have modules like `V1.hs`, `V2.hs`, etc. Each has their own `Schemas` type and a migration from the previous one.
basically, yes. Although I don't do one for each table, but just introduce a new `Vn.hs` each time I need to change the schema. So the first schema I defined...
You can of course break apart that first one however you like. As for maintainability though, I never change the old `Vn.hs`s, just introduce a new one.
Hmmm, that looks tricky and a little complex with the use of `AppendSymbol`, but perhaps worth a try. I might instead use the `row` (or even `rowStar`) function to store...
I'm open to a PR
I'm open to a PR for this, although migrations have gone thru a bit of change in the dev branch.
The `postgresql-libpq-notify` library is now at v0.2.0. Bug @jfischoff to pair on Squeal bindings.
#71 adds the operators `>*` and `*
`Divisible f` is equivalent to `(Contravariant f, forall x. Monoid (f x))`. It is also equivalent to a monoid object enriched in the category of `Contravariant`s with unit given by...