Vamshi Surabhi

Capturing postgres errors and propagating them to the client side is easy however we shouldn't be capturing every error, only those that are meant for the client. The question is...

@abn This is definitely something that we want to implement but we haven't added it to our pipeline yet. Hopefully, we can get this out in a couple of releases.

@heyrict One of the biggest challenges/decisions with event based subscriptions is how does the client recover from loss of events? Does the server store what events are delivered to clients?...

@daniel-chambers Given the changes in graphql-engine since this issue has been created, I think it makes more sense for this to be per 'source' customization configuration. Essentially extend the `SourceCustomization`...

The schema generation logic respects the nullability of columns in the database. Can you give us an example where this is not as expected?

Unfortunately `NOT NULL` constraint does not imply that the column value **needs** to be provided to insert a row. A column can have a `NOT NULL` constraint with a `DEFAULT`...

@rccoe > you can't pass a dynamic JSON $where as a parameter to a SQL function This use case will be supported in a future iteration. For example: ```yaml parameterized_queries:...

If we go with `raw`, what does it mean to use functions like [`arrayValue`](http://hackage.haskell.org/package/hasql-0.19.12/docs/Hasql-Encoders.html#v:arrayValue) on `raw`?

How about this? ``` haskell rawList :: Params [(LibPQ.Oid, Maybe ByteString)] rawList = Params (Params.Params $ Op encoder) where encoder = DList.fromList . map (fmap const) ```

Or rather ``` haskell rawList :: Params [(LibPQ.Oid, Bool -> Maybe ByteString)] rawList = Params (Params.Params $ Op DList.fromList) ```