Jason Kraus
Jason Kraus
Expanding on this, class methods that return a queryset like `get_root_nodes` & `get_ancestors` should also be implemented as a queryset.
Using postgres as well, I have noticed that on a new database I run `schema:sync` and it will create the tables, drop all id columns, drop constrains, recreate all dropped...
Curious what model or library would be used to complete this. Edit: this might work: https://www.npmjs.com/package/compact-prediction-tree
Currently getting bit by this as well, requires extra record keeping. Fun :(
We're using a fork of this in production. What is blocking this from being merged? I would be glad to simplify our build process ;)
Github pages doesn't respect Gemfiles, so this might still be useful for some people
Also had this when I set AWS_DEFAULT_ACL='public-read'
Also reported as issue #135
Ran into this as well. [x] 0.2.25
I believe this is also impacting `django-select2`. Allot of these external integrations assume a proper many2many field and data is getting munged in the handling between (from widget to field...