rd-parse
potygen
| rd-parse | potygen | |
|---|---|---|
| 1 | 4 | |
| 102 | 100 | |
| 0.0% | 0.0% | |
| 0.0 | 2.8 | |
| almost 2 years ago | over 1 year ago | |
| JavaScript | TypeScript | |
| 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.
rd-parse
-
Pql, a pipelined query language that compiles to SQL (written in Go)
I also wrote a parser (in typescript) for postgres (https://github.com/ivank/potygen), and it turned out quite the educational experience - Learned _a lot_ about the intricacies of SQL, and how to build parsers in general.
Turned out in webdev there are a lot of instances where you actually want a parser - legacy places where they used to save things in plane text for example, and I started seeing the pattern everywhere.
Where I would have reached for some monstrosity of a regex to solve this, now I just whip out a recursive decent parser and call it a day, takes surprisingly small amount of code! (https://github.com/dmaevsky/rd-parse)
potygen
-
Sqlc: Compile SQL to type-safe code
There was a saying that before learning postgres in depth, the db is just a dumb store of data for devs, once you spend time to learn the tools it provides though, most applications just look like a very thin layer on top of the sql.
There is so much more to rdbms (especially pg) than just joins - common table expressions, window functions, various views, let alone all the extensibility - extensions, custom types, even enums.
All of that can enable writing performant, type safe and very compact applications.
I am yet to see libs that embrace the elegance of it all - I’ve attempted this once - https://github.com/ivank/potygen but didn’t get much traction. I’m now just waiting for someone more determined to pick up those ideas - a client lib that exposes the type safety and intellisence at compile time and allows you to easily compose those sql queries.
I think this project has some ways to go to reach that though, but thankfully it is a step in the right direction.
-
Monodraw
OMG this is one of my favorite tools paid for it all the way back when it went out. Have used it so many times just to write documentation for things like:
https://github.com/ivank/potygen/blob/main/packages/potygen/...
ASCII is just so versatile and allows you to put nice graphics in places where one does not expect, making things more easily understandable.
-
Pql, a pipelined query language that compiles to SQL (written in Go)
I also wrote a parser (in typescript) for postgres (https://github.com/ivank/potygen), and it turned out quite the educational experience - Learned _a lot_ about the intricacies of SQL, and how to build parsers in general.
Turned out in webdev there are a lot of instances where you actually want a parser - legacy places where they used to save things in plane text for example, and I started seeing the pattern everywhere.
Where I would have reached for some monstrosity of a regex to solve this, now I just whip out a recursive decent parser and call it a day, takes surprisingly small amount of code! (https://github.com/dmaevsky/rd-parse)
- Is ORM still an anti-pattern?
What are some alternatives?
pql - Pipelined Query Language
NORM - NORM - No ORM framework
Preql - An interpreted relational query language that compiles to SQL.
SQLPage - Fast SQL-only data application builder. Automatically build a UI on top of SQL queries.
tenzir - Tenzir is the data pipeline engine for security teams.
sqlite-fast - A high performance, low allocation SQLite wrapper targeting .NET Standard 2.0.