Using #haskell persistent's abstractions for queries and dealing with SQL feels like a mistake compared to just dealing with raw #postgresql. In the future I may look into an alternative. Using #scotty. The benefit of the database-agonisticism is outweighed by the fact that specific postgresql stuff is used at times *and* the abstractions are difficult to work with because of the documentation and the amount of code being generated that I have to work with.
@someodd I've been programming for a long time. I can't believe how long it takes to figure out how to perform very basic database queries using this library. Not only that but it has absurd limitations. For example, you can't seem to select only specific fields, you can only select keys *or* everything from the database record. Unacceptable. Am I wrong?
Also, I've always disliked generated code as far back as I can remember encountering the concept. It's particularly bad with Persistent because you have to work so much with these generated types and the documentation for such isn't great and it all feels hidden, opaque.
@dpwiz That's very true. Although, coming from other languages, it was surprising how building a simple CRUD REST API is significantly more challenging and lacks modern features with #scotty and the like. There have been some advantages I have liked playing with this library, though.