aquameta
blog
| aquameta | blog | |
|---|---|---|
| 8 | 11 | |
| 1,092 | 9 | |
| 0.0% | - | |
| 8.0 | 6.0 | |
| 4 months ago | 3 months ago | |
| PLpgSQL | ||
| GNU General Public License v3.0 only | Creative Commons Zero v1.0 Universal |
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.
aquameta
-
Versioning data in Postgres? Testing a Git like approach
Aquameta has an interesting extension that something like this in a different way: https://github.com/aquametalabs/aquameta/tree/master/extensi....
-
You Can Now Code Websites with SQL
Related: Web development platform built entirely in PostgreSQL - https://github.com/aquametalabs/aquameta
- Just Use Postgres for Everything
- Aquameta is a web stack mostly in Postgres
- How to really use Postgres for literally everything.
-
What is the best way of implementing versions/revisions/history on a Postgres database?
I've never used this but it looks interesting https://github.com/aquametalabs/aquameta/tree/master/extensions/bundle
blog
- Versioning data in Postgres? Testing a Git like approach
-
A Different Type of SQL Recursion with PostgreSQL
Originally published at https://github.com/vb-consulting/blog/discussions/1
A follow up on this article was written today
[Recursion with PostgreSQL, Follup 1, Perfomances](https://github.com/vb-consulting/blog/discussions/4)
-
Recursion with PostgreSQL Follow-Up 3 - Finding the Right Path
In my previous article, I managed to get some really crazy performances in tree processing by using PostgreSQL recursive procedural-style function.
- Recursive Hierarchical Queries in SQL: A Deep Dive into Employee Level
- Which Way .NET Developer?
-
Recursion with PostgreSQL, Follup 1, Perfomances
I wrote a follow-up on yesterday's article on tree processing and recursion with PostgreSQL. This one: https://github.com/vb-consulting/blog/discussions/1
SQL was never intended for this kind of stuff; I'm sure that Fabian Pascal will tell us all about it.
And indeed, recursive CTEs are awful, confusing, and severely limited ... but they look cool and smart, and smart people use them (I hate them).
In any case, I used a procedural approach to this problem and, with a few smart optimizations, managed to squeeze some really spectacular performances (757K tree records with 20K unique nodes in just 5 seconds without any indexes, so it probably can go even faster).
What are some alternatives?
omdb-postgresql - PostgreSQL Schema for OMDB
Logidze - Database changes log for Rails
snowfs - SnowFS - a fast, scalable version control file storage for graphic files :art:
pgkit - Pgkit - Backup, PITR and recovery management made easy
duckdb_fdw - DuckDB Foreign Data Wrapper for PostgreSQL
Architecture-of-consoles - Technical articles about console architecture
klapa - Text patterns clustering in PostgreSQL
developer-handbook - An opinionated guide on how to become a professional Web/Mobile App Developer.
pgreplay - pgreplay reads a PostgreSQL log file (*not* a WAL file), extracts the SQL statements and executes them in the same order and relative time against a PostgreSQL database cluster.
blog - OpenSource,Database,Business,Minds. git clone --depth 1 https://github.com/digoal/blog
RssDotnet - A list of my favourite dotnet RSS feeds