malloy
PluSQL
| malloy | PluSQL | |
|---|---|---|
| 19 | 2 | |
| 1,827 | 7 | |
| 1.4% | - | |
| 9.8 | 10.0 | |
| 10 days ago | over 8 years ago | |
| TypeScript | PHP | |
| MIT License | GNU General Public License v3.0 or later |
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.
malloy
- Malloy: A language for describing data relationships and transformations
- Malloy: Open-source language for analyzing, transforming, and modeling data
- Malloy
-
Upcoming Data Engineering Tools
Rust and python combination has resulted in some amazing python libraries. One interesting thing I see is people developing different variety of query languages like EdgeQL and Malloy
- Malloy: An Experimental Language for Data
-
I don't need your query language
I felt the same way when Malloy[0] launched. It has some interesting features, but I couldn't see myself ever using it. Nothing makes a big enough difference to spend the time to learn it.
Would love to hear from anybody that's using it regularly
0 - https://www.malloydata.dev/
-
When not to use SQL - Sean J Taylor
Sidenote: have you used Google Malloy? If so, what did you like/dislike?
PluSQL
-
I don't need your query language
I feel exactly the same way about ActiveRecord ORMs. That’s why I created PluSQL:
https://github.com/iaindooley/PluSQL
-
Case against OOP is understated, not overstated
"The saddest thing about the "object–relational impedance mismatch" is that the focus went totally to the wrong side. The relational model is a much nicer way to model relations than a graph of objects (that's the whole point after all)."
I found the same thing. When I was using ORMs I always found them clunky for all but the simplest tasks, where I would long for an easy way to use SQL and have it "just work" for objects, so I created this:
https://github.com/iaindooley/PluSQL
It's obviously not been maintained but I think it's a model that has legs: that is, simply the creation of SQL with some convenience methods, allow the use of completely arbitrary SQL, and then intuit the object mapping automatically without loading the entire result set into memory.
What are some alternatives?
prql - PRQL is a modern language for transforming data — a simple, powerful, pipelined SQL replacement
PostgreSQL - Mirror of the official PostgreSQL GIT repository. Note that this is just a *mirror* - we don't work with pull requests on github. To contribute, please see https://wiki.postgresql.org/wiki/Submitting_a_Patch
logica - Logica is a logic programming language that compiles to SQL. It runs on Google BigQuery, PostgreSQL and SQLite.
dotty
Preql - An interpreted relational query language that compiles to SQL.
partiql-lang-kotlin - PartiQL libraries and tools in Kotlin.
rfcs - RFCs for major changes to EdgeDB
spyql - Query data on the command line with SQL-like SELECTs powered by Python expressions
xsuspender - :eyes: :computer: :zzz: :battery: Save battery by auto-suspending unfocused X11 applications.
Sift - Sift is a basic, Relational Algebra based query engine built on top of Apache Arrow. It draws inspiration from Andy Grove's KQuery.
BQL - BQL: A Better Query Language, SQL Superset
tresql - Shorthand SQL/JDBC wrapper language, providing nested results as JSON and more