zheap
django-simple-history
| zheap | django-simple-history | |
|---|---|---|
| 3 | 4 | |
| 88 | 2,095 | |
| - | 1.4% | |
| 10.0 | 8.1 | |
| over 3 years ago | 3 days ago | |
| HTML | Python | |
| - | BSD 3-clause "New" or "Revised" 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.
zheap
-
Tracking down high CPU Utilization on Amazon Aurora PostgreSQL
Hoping something like the zheap storage engine initiative should help us get past these bottlenecks in the future. Until then we may not be able to prevent the bloat but could certainly minimize the impact.
-
Building an interface (even if there's only one implementation) is always right
Hey, OP here -- it is a bit odd and also possibly immature to be so harsh on MySQL apropos of nothing. That said, I intended more to be pro-Postgres rather than anti-MySQL (it's a great piece of software, other DBs and Postgres learn from it all the time, zheap[0] exists to replicate what they've built, for example).
I also have to admit that I definitely want postgres every time I see MySQL. Maybe I need to read more on just how easy and amazing MySQL can be. Links welcome!
[0]: https://cybertec-postgresql.github.io/zheap/
-
Databases in 2021: A Year in Review
Postgres's dominance is well deserved, of course. My only concerns with it, both are actively worked on, are bloat management (significant for update heavy workloads and programmers used to the MySQL model of rollback segments) and the scaling of concurrency (going over 500 connections). Bloat was taken over by Cybertec[1] after stalling for a bit and is funded (yay), while concurrency was also enhanced out of Microsoft [2]. All in all, an excellent future for our beloved Postgres.
[1] https://github.com/cybertec-postgresql/zheap
django-simple-history
-
What are the differences between django-auditlog and django-simple-history?
I would like to know what is the differences and use cases of these two django packages: django-auditlog and django-simple-history.
-
Databases in 2021: A Year in Review
Would love to see wider support for temporal tables, but application level approaches like https://github.com/jazzband/django-simple-history have worked for the business issues I have.
-
Django package for creating data history or checkpoints for database model
Searching djangopackages.org I was confoosed by django-field-history, "A Django app to track changes to a model field.", and similar apps django-reversion and django-simple-history, I think these are tracking changes to the model itself--the code--inside of admin? Like if you created a Poll which saved results to the database, and later wanted to change one of the Poll questions?
-
create a timeline for model object changes
If you're looking to track for users, maybe something like django-simple-history? https://github.com/jazzband/django-simple-history
What are some alternatives?
sysbench - Scriptable database and system performance benchmark
django-reversion - django-reversion is an extension to the Django web framework that provides version control for model instances.
dbdb.io - The On-line Database of Databases
django-auditlog - A Django app that keeps a log of changes made to an object.
zombodb - Making Postgres and Elasticsearch work together like it's 2023
django-audit-log - Audit log for your Django models
pev2 - Postgres Explain Visualizer 2
django-easy-audit - Yet another Django audit log app, hopefully the simplest one.
clickhouse-operator - Altinity Kubernetes Operator for ClickHouse creates, configures and manages ClickHouse clusters running on Kubernetes
django-field-history - A Django app to track changes to model fields.
vitess - Vitess is a database clustering system for horizontal scaling of MySQL.