Our great sponsors
- SonarQube - Static code analysis for 29 languages.
- ONLYOFFICE ONLYOFFICE Docs — document collaboration in your environment
- InfluxDB - Access the most powerful time series database as a service
|15 days ago||over 1 year ago|
|BSD 3-clause "New" or "Revised" License||MIT License|
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.
What's your favorite Database EDSL/library in Haskell?
4 projects | reddit.com/r/haskell | 28 Feb 2023
If you ever have any questions about Opaleye I'm happy to help. Feel free to open an issue to ask about anything any time.
Persistent vs. beam for production database
2 projects | reddit.com/r/haskell | 9 Feb 2023
Sounds like Opaleye isn't on your list of choices, but if it is then feel free to ask me any questions, any time by filing an issue (I'm the Opaleye maintainer).
What are things that the Haskell scene lacks the most?
4 projects | reddit.com/r/haskell | 21 Apr 2022
Out of memory when building product-profunctors
2 projects | reddit.com/r/haskell | 13 Mar 2022
Nice! Well done. If you have any more questions about product-profunctors or Opaleye then please let me know. It's best to ask by [opening an issue](https://github.com/tomjaguarpaw/haskell-opaleye/issues/new).
8 projects | news.ycombinator.com | 10 Jul 2021
The only way out that I can see is to design embedded domain specific languages (EDSLs) that inherit the expressiveness, composability and type safety from the host language. That's what Opaleye and Rel8 (Postgres EDSLs for Haskell do. Haskell is particularly good for this. The query language can be just a monad and therefore users can carry all of their knowledge of monadic programming to writing database queries.
This approach doesn't resolve all of the author's complaints but it does solve many.
Disclaimer: I'm the author of Opaleye. Rel8 is built on Opaleye. Other relational query EDSLs are available.
Show HN: PRQL 0.2 – Releasing a better SQL
16 projects | news.ycombinator.com | 27 Jun 2022
> Joins are what makes relational modeling interesting!
It is the central part of RM which is difficult to model using other methods and which requires high expertise in non-trivial use cases. One alternative to how multiple tables can be analyzed without joins is proposed in the concept-oriented model  which relies on two equal modeling constructs: sets (like RM) and functions. In particular, it is implemented in the Prosto data processing toolkit  and its Column-SQL language. The idea is that links between tables are used instead of joins. A link is formally a function from one set to another set.
 Joins vs. Links or Relational Join Considered Harmful https://www.researchgate.net/publication/301764816_Joins_vs_...
 https://github.com/asavinov/prosto data processing toolkit radically changing how data is processed by heavily relying on functions and operations with functions - an alternative to map-reduce and join-groupby
Excel 2.0 – Is there a better visual data model than a grid of cells?
5 projects | news.ycombinator.com | 31 Mar 2022
One idea is to use columns instead of cells. Each column has a definition in terms of other columns which might also be defined in terms of other columns. If you change value(s) in some source column then these changes will propagate through the graph of these column definitions. Some fragments of this general idea were implemented in different systems, for example, Power BI or Airtable.
This approach was formalized in the concept-oriented model of data which relies on two basic elements: mathematical functions and mathematical sets. In contrast, most traditional data models rely on only sets. Functions are implemented as columns. The main difficulty in any formalization is how to deal with columns in multiple tables.
This approach was implemented in the Prosto data processing toolkit: https://github.com/asavinov/prosto
Show HN: Query any kind of data with SQL powered by Python
6 projects | news.ycombinator.com | 25 Jan 2022
Having Python expressions within a declarative language is a really good idea because we can combine low level logic of computations of values with high level logic of set processing.
A similar approach is implemented in the Prosto data processing toolkit:
Although Prosto is viewed as an alternative to Map-Reduce by relying on functions, it also supports Python User-Defined Functions in its Column-SQL:
Show HN: Hamilton, a Microframework for Creating Dataframes
6 projects | news.ycombinator.com | 8 Nov 2021
Hamilton is more similar to the Prosto data processing toolkit which also relies on column operations defined via Python functions:
However, Prosto allows for data processing via column operations in many tables (implemented as pandas data frames) by providing a column-oriented equivalents for joins and groupby (hence it has no joins and no groupbys which are known to be quite difficult and require high expertise).
Prosto also provides Column-SQL which might be simpler and more natural in many use cases.
The whole approach is based on the concept-oriented model of data which makes functions first-class elements of the model as opposed to having only sets in the relational model.
8 projects | news.ycombinator.com | 10 Jul 2021
One alternative to SQL (type of thinking) is Column-SQL  which is based on a new data model. This model is relies on two equal constructs: sets (tables) and functions (columns). It is opposed to the relational algebra which is based on only sets and set operations. One benefit of Column-SQL is that it does not use joins and group-by for connectivity and aggregation, respectively, which are known to be quite difficult to understand and error prone in use. Instead, many typical data processing patterns are implemented by defining new columns: link columns instead of join, and aggregate columns instead of group-by.
More details about "Why functions and column-orientation" (as opposed to sets) can be found in . Shortly, problems with set-orientation and SQL are because producing sets is not what we frequently need - we need new columns and not new table. And hence applying set operations is a kind of workaround due the absence of column operations.
This approach is implemented in the Prosto data processing toolkit  and Column-SQL is a syntactic way to define its operations.
 https://github.com/asavinov/prosto Prosto is a data processing toolkit - an alternative to map-reduce and join-groupby
 https://prosto.readthedocs.io/en/latest/text/column-sql.html Column-SQL (work in progress)
 https://prosto.readthedocs.io/en/latest/text/why.html Why functions and column-orientation?
Feature Processing in Go
3 projects | news.ycombinator.com | 21 Dec 2020
(Currently, it is not actively developed and the focus is moved to a similar project - https://github.com/asavinov/prosto - also focused on data preprocessing and feature engineering)
What are some alternatives?
esqueleto - Bare bones, type-safe EDSL for SQL queries on persistent backends.
HDBC - Haskell Database Connectivity
database-migrate - database-migrate haskell library to assist with migration for *-simple sql backends.
HongoDB - A Simple Key Value Store
squeal-postgresql - Squeal, a deep embedding of SQL in Haskell
rel8 - Hey! Hey! Can u rel8?
opaleye-classy - Classy MTL extension of the lovely Opaleye library.
Preql - An interpreted relational query language that compiles to SQL.
fquery - A graph query engine