fx
By nikita-volkov
hasql-dynamic-statements
Dynamic statements for Hasql (by nikita-volkov)
fx | hasql-dynamic-statements | |
---|---|---|
- | 1 | |
0 | 5 | |
- | - | |
0.0 | 6.1 | |
about 2 years ago | about 1 month ago | |
Haskell | Haskell | |
MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
fx
Posts with mentions or reviews of fx.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning fx yet.
Tracking mentions began in Dec 2020.
hasql-dynamic-statements
Posts with mentions or reviews of hasql-dynamic-statements.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-02-09.
-
Persistent vs. beam for production database
In typical CRUD applications you can get a long way with type-checked plain SQL and tuples via hasql-th, which is a great time saver at prototyping. Later on when you have more conditional logic in your queries you can gradually substitute it with dynamic statements. It works very well in production where you incrementally refine your own high-level abstractions with appropriate encoders/decoders, you can even build your own DSL on top of it, instead of relying on pre-defined query building APIs of Persistent and Beam. But again, both Persistent and Beam will work well too.