django-computedfields icon indicating copy to clipboard operation
django-computedfields copied to clipboard

Provides autogenerated autoupdated database fields for model methods.

Results 36 django-computedfields issues
Sort by recently updated
recently updated
newest added

These are somewhat hard to test automatically with all their arguments (thus currently skipped in coverage). Needs a good story how to approach them from unit tests.

Currently db interactions simply route to 'default' connection without any means to change that through the API. TODO: - investigate on custom db routers, esp. for the read vs. write...

enhancement

In `bulk_updater` we do a DISTINCT on every query in question. This is needed to avoid updating 1:n relations over and over. Issues with this: - DISTINCT is placed there...

enhancement

Currently coveralls marks a CI run as failed for a tiny decrease in coverage. Check if there is a threshold setting to get it less noisy.

Shall fix #56. This is just a proof of concept currently with hacked in signal dispatching for `update_dependent`. TODO: - apply data aggregation on all resolver parts including handler code...

Adding back support for Django 2.1

Coming from the discussion in #49. We should establish some way of getting notified when CFs are getting updated by the resolver. There are several ways to achieve this, mainly...

enhancement

i'm in the case of computed field depending on fields on a model on the otherside of M2M relation and also of fields in intermediate model. (I have followed the...

There might be a serious bug here. Afaiu `local()` is that resolves to the correct context when it's attribute is accessed from inside the running thread. Here you access the...

bug