sqlalchemy-easy-softdelete
ibis
| sqlalchemy-easy-softdelete | ibis | |
|---|---|---|
| 3 | 24 | |
| 49 | 4,304 | |
| - | 7.9% | |
| 2.7 | 10.0 | |
| about 1 month ago | 6 days ago | |
| Python | Python | |
| GNU General Public License v3.0 or later | Apache License 2.0 |
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.
sqlalchemy-easy-softdelete
- SQLAlchemy “SQL Man-in-the-middle” for soft-deleted entities
- Sqlalchemy-Easy-Softdelete: SQL Man-in-the-Middle for SQLAlchemy
-
Easy, alternative soft deletion: `deleted_record_insert`
I wrote a specific library to do this (automatically generates a mixin for SQLAlchemy and installs a hook which rewrites all queries, removing soft-deleted items from queries and also relationships) so that the soft-delete problem becomes a non issue and you still have the data there if you want to revert/activate something
https://github.com/flipbit03/sqlalchemy-easy-softdelete
ibis
-
Show HN: Hashquery, a Python library for defining reusable analysis
I really don't understand the appeal of dbt vs a proper programming language. The templating approach leads to massive spaghetti. I look forward to trying out something like Ibis [0]
0: https://ibis-project.org/
-
This Week In Python
ibis – portable Python dataframe library
- Ibis: The portable Python dataframe library
- FLaNK Stack 26 February 2024
-
Quarto
The main benefit is that you get a Python (or R, Julia or Rust) interpreter. So you can evaluate code. A good example of the value of this is the Ibis docs which use Quarto: https://ibis-project.org/
-
Polars – A bird's eye view of Polars
Ive found polars quite intuitive, though for python, I lean more towards [ibis](https://ibis-project.org/). The interface is nearly identical, but ibis has the benefit if building sql queries before pulling any actual data (like dbplyr) — whereas polars requires the data to be in-memory (at least for rdb’s, though correct me if Im wrong)
this to me seems like a good argument for only using ibis, but Im happy to be convinced otherwise
- Ibis – Universal Interface for Data Wrangling
-
Vanna.ai: Chat with your SQL database
Please add Ibis Birdbrain https://ibis-project.github.io/ibis-birdbrain/ to the list. Birdbrain is an AI-powered data bot, built on Ibis and Marvin, supporting more than 18 database backends.
See https://github.com/ibis-project/ibis and https://ibis-project.org for more details.
- Ibis
What are some alternatives?
awesome-data-temporality - A curated list to help you manage temporal data across many modalities 🚀.
snowflake-connector-python - Snowflake Connector for Python
flask-sqlalchemy - Adds SQLAlchemy support to Flask [Moved to: https://github.com/pallets/flask-sqlalchemy]
PySpark-Boilerplate - A boilerplate for writing PySpark Jobs
macaroon - Postgres introspection and macros
Apache Impala - Apache Impala
SQLAlchemy - The Database Toolkit for Python
pangres - SQL upsert using pandas DataFrames for PostgreSQL, SQlite and MySQL with extra features
sqlite_scanner - DuckDB extension to read and write to SQLite databases
katacoda
nodejs-polars - nodejs front-end of polars
django-clickhouse - This project's goal is to build Yandex ClickHouse database into Django project.