Jakub Ryška

OK, thanks for noticing

One option, how to do this would be to use something similar to the `Writer`, with the difference in the `a` type, something like this: ``` newtype SchemaMaker read dummy...

So you mean, that the table properties would get one more field: ``` data TableProperties writerColumns viewColumns = TableProperties (Writer writerColumns viewColumns) (View viewColumns) ColumnDescription ``` and the information, how...

How would that look like? I'm imagining, that the referencing of foreign key could work like `runUpdate`, the `required` would accept a `Table` and a function `read -> Column a`....

Regarding the foreign keys, what about this signature: ``` foreignKey :: (D.Default FKMaker from from' , D.Default FKMaker to to' D.Default U.Unpackspec fk fk) => Table a0 from -> (from'...

At which point can the user change the `Column` in the `Table`? You mean something like: 1. User defines a Table: `table1 :: Table (Column PGInt4) (Column PGInt4)` 2. User...

I meant that it we consider the situation I explained a bad thing, that the user can somehow create a new table from an existing definition and then using it...

So can you, please, point out, where the application of the operator before running the `foreignKey` would happen? Which function the user will apply , from `Table` to `Table` in...

So if the type held under `View` from the `Internal.Table` module will be effectively changed to `TableColumn a`, then the `ColumnMaker` instance needed for querying tables of would be this...

Maybe we can have these two variants together, `required` would create `Table` with `Column`s, whereas some other variant, for example `required'` would create `Table` with `TableColumn`s. There would be needed...