Leon P Smith

Oh fun, now we are talking three ways of catching exceptions, MonadCatchIO-mtl, MonadCatchIO-transformers, and monad-control. I'd forgotten that MonadCatchIO-mtl and MonadCatchIO-transformers are completely separate, incompatible packages. (though of a similar...

How important is streaming to your intended application? You could generalize `query` and `execute` yourself, which need not be concerned with controlling exceptions. Also, you could open a cursor for...

Well, using a database cursor is not particularly difficult. See [close](http://www.postgresql.org/docs/9.1/static/sql-close.html), [declare](http://www.postgresql.org/docs/9.1/static/sql-declare.html), [fetch](http://www.postgresql.org/docs/9.1/static/sql-fetch.html), and [move](http://www.postgresql.org/docs/9.1/static/sql-move.html) for details.

Yeah, the exceptions package is very much in the spirit of `MonadCatchIO`, though with the updated mask functions and with some of the problematic instances removed. Honestly, I think I...

Are you looking to use PostgreSQL's geometry types, or PostGIS's? Yeah, there is no specific support for either variety at this point. However you don't have to modify postgresql-simple to...

Well, yes, I do make use of user defined types, so this sort of flexibility is essential to me (and in fact a major reason for abandoning HDBC). The Param...

Oh, and I forgot to mention; it's important that your Result instances not retain a reference to the ByteString that `convert` is passed, as that will cause the entire LibPQ.Result...

Oh, no problem :)

You are correct, that's the recommended way of type-checking postgresql types that do not have stable type OIDs, as describes all user-added types. And no, it's not _exactly_ a languishing...

Well, the exact exception that should be thrown in some cases is not all that well thought out or even wrong by my current standards. I try to throw IOExceptions...