Codey Oxley

Having this flexibility could be nice I think. It could help people who don't want to use attribute name prefixing to do similar grouping. As far as querying, `attr.key` but...

This might be useful advice: https://medium.com/@eduardosilva/django-rest-framework-why-you-should-avoid-the-depth-option-f6adbf1b24#.jjst2k8aa I'll continue to investigate

https://docs.djangoproject.com/en/dev/ref/models/querysets/#select-related This seems pretty feasible, though I wish it was less explicit. We could generate the viewset queryset, adding `select_related` for everything in: ``` python .select_related(*[i.replace('_id', '') for i in...

@jathanism: Woo!... kind of. I have hooks "working". Meaning, everything that should work works except for the fact that this module **forces** you to have user attribute per model meaning...

Also, https://github.com/PressLabs/django-rest-hooks-ng Without looking too much into it, this appears to be more what we're after with global hooks. It's a fork of django-rest-hooks, but apparently it changes the schema...

@jathanism That's what I assumed which is why if you look at [https://github.com/dropbox/nsot/compare/master...coxley:hooks](my fork) you'll see that's what I did. The issue I linked is pretty fresh and that line...

@jathanism Just got around to checking the other project and it just allows you to specifiy `global_hook` as a bool in the payload when creating a hook. In other words,...

Just an update here: Following IRC conversations we came to the realization that this would be way more elegant if implemented solely on the `Change` model considering everything ends up...

Could the check that judges if value is compatible with multi not be re-used for default_value?

That worked but I guess it's just not setup to provide the logging if threading isn't being done because that leaves it blank until finish.