django-postgres-extra
django-postgres-extra copied to clipboard
Bringing all of PostgreSQL's awesomeness to Django.
`insert_and_get` doesn't get anything when using `ConflictAction.NOTHING` and if there is a conflict. The documentation is not very clear on this point https://django-postgres-extra.readthedocs.io/en/master/conflict_handling.html#insert-vs-insert-and-get On https://django-postgres-extra.readthedocs.io/en/master/conflict_handling.html#conflictaction-nothing, it says > This applies...
### Introduction Django's `field.pre_save()` allows fields to auto-provide 2 different values: 1 for `insert`, and 1 for `update`. There is no requirement of what these values are: they could be...
It would be convenient if you could pass model instances to bulk_insert/bulk_upsert and not just dicts.
As suggested in https://github.com/SectorLabs/django-postgres-extra/pull/135#issuecomment-800692846 it would be convenient if `bulk_insert`/`bulk_upsert` had a `batch_size` parameter and would automatically chunk your rows accordingly.
`_get_upsert_fields` should not add fields in `self.conflict_target` in the `update_fields` If we are "on conflict" then we know that the `conflict_target` columns already contains the value we wanted to insert,...
In native postgres, I can create stand-alone `SEQUENCE` objects that are sometimes useful outside of a primary key context. It would be nice if there was a `Sequence` class similar...
I have an insert query where I would like to have the database generate some field using a sequence. At the moment, Django does not return the generated field from...
This is more a long-term thing. Probably not going to happen any time soon. https://www.postgresql.org/docs/9.1/static/queries-with.html
https://www.postgresql.org/docs/9.3/static/sql-creatematerializedview.html