Logidze
blog
Logidze | blog | |
---|---|---|
6 | 11 | |
1,557 | 9 | |
- | - | |
5.5 | 6.0 | |
2 months ago | 3 months ago | |
Ruby | ||
MIT License | 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.
Logidze
-
Versioning data in Postgres? Testing a Git like approach
There's an interesting approach to it that works with Rails and PostgreSQL using triggers.
https://github.com/palkan/logidze
- Database changes log for Rails
-
Best rails tools to automatically handle logging of things like all a user's actions, or changes to a record in a module - primarily for audit purposes.
https://github.com/palkan/logidze is my favorite for these kind of things
-
How would you build an audit log in Rails for a high-throughput API?
Have you considered https://github.com/palkan/logidze ?
- Temporality/time-travelling in DB with ActiveRecord?
-
Is it a terrible idea to manually create a table in a MySQL database generated by a rails model?
Something like this might be an option? https://github.com/palkan/logidze
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?
PaperTrail - Track changes to your rails models
pgkit - Pgkit - Backup, PITR and recovery management made easy
Audited - Audited (formerly acts_as_audited) is an ORM extension that logs all changes to your Rails models.
Architecture-of-consoles - Technical articles about console architecture
marginalia - Attach comments to ActiveRecord's SQL queries
developer-handbook - An opinionated guide on how to become a professional Web/Mobile App Developer.
Destroyed At - ActiveRecord Mixin for Safe Destroys
aquameta - Web development platform built entirely in PostgreSQL
rails_or - Cleaner syntax for writing OR Query in Rails 5, 6. And also add #or support to Rails 3 and 4.
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.
Paranoia - acts_as_paranoid for Rails 5, 6 and 7
RssDotnet - A list of my favourite dotnet RSS feeds