tilapia VS haskelldb

Perhaps the documentation for Char should contain examples of how you write the literals. Tracking as https://github.com/tomjaguarpaw/tilapia/issues/128

Can you please report concrete examples here: https://github.com/tomjaguarpaw/tilapia/issues/new

I'll do what I can to improve the situation, but I need to know which packages precisely you are talking about.

Thanks! Tracking at https://github.com/tomjaguarpaw/tilapia/issues/109

It would be nice with a "modern cabal for stack users" tutorial (ddg tells me it's an issue https://github.com/tomjaguarpaw/tilapia/issues/11 ), answering questions like

If you're on Windows and you're feeling brave you could try these new instructions developed by a collaborator of mine over at the tilapia project. If anything goes wrong with those instructions then please put a message on the pull request describing what the problem was and we'll try to get it fixed.

Great! I'd be happy to have you on board. Please "Watch" the repo so that you are notified of discussions that happen there. Feel free to start your own discussions at any time by opening an issue.

Feel free to collaborate with me on Tilapia. At the very least I would welcome knowing about your ideas.

I also have a personal project (tilapia) for tracking difficulties in the Haskell ecosystem. Feel free to post any observations, questions or difficulties there.

HaskellDB was principled but the codebase was somewhat bitrotted, it had dubious denotational semantics, it was possible to write crashing queries. and only worked with a special "record" form data types that it had cooked up. On the other hand once one accepted the special "records" everything else looked like familiar Haskell. Queries were written in do-notation.