Closed ghost closed 5 years ago
It definitely would make a lot of sense to split the Protocol
module off into a different package. There are some requirements the higher-level stuff has on particular functionality that many lower levels don't provide, but postgresql-libpq at least should be able to do most of it, with some performance overhead. I talked to Nikita Volkov (the author of hasql) about a year ago about some of this, and it sounded like he was working on building a new backend layer that could potentially be shared with postgresql-typed, so I should also check in on updates there.
You can re-open if you want. I am not looking to use this split currently.
This would help the library stay resilient to the future as it could switch to using postgresql-simple or a lower library in the future as postgresql server evolves
(Feel free to close if this isn't of interest).