Saurabh Nanda

So, let's benchmark the following use-cases: * Fetch a complete row by PK * Fetch a complete row by a bunch of WHERE clauses * Fetch few columns by PK...

Why has `prepareQuery` been marked as deprecated? It is being superseded by which function?

I think in view of #476 this issue should be re-opened. Probably prepare if for Hackoberfest so that we can tackle this as a community and get it fixed once...

Hey, should i spruce this up for the latest version? I have a bunch of other chapters that I didn't manage to publish. But this might be the required push...

Please give me a few more days. I'm on it -- just got side-tracked with my static-site builder. On Sun, Aug 23, 2020 at 2:12 PM tomjaguarpaw wrote: > @saurabhnanda...

@tomjaguarpaw I finally got around to finishing my static site builder and am now revamping the tutorial. Even when I was writing the first one, I was unable to explain...

I'm getting used to the new API myself, I think my previous comment should read as `Field a` vs `FieldNullable a`, right?

the API has changed **significantly** since 0.5-0.6 that we are using in production. Is `runInsert_` really the user-facing API now? It requires a user to understand many data-types to construct...

Is there any reason why [Returning a b](https://hackage.haskell.org/package/opaleye-0.7.0.0/docs/Opaleye-Internal-Manipulation.html#t:Returning) doesn't have a `ReturnNothing` constructor? Does Postgres insist on returning _something_ in every `INSERT` statement?

I had this note in my old tutorial. Is there a technical explanation for why the API behaves this way (`runSelect` doesn't force you to call `fromFields` on its output,...