search

sehughes / django-treebeard

Automatically exported from code.google.com/p/django-treebeard
Apache License 2.0
0 stars 0 forks source link

some refactoring and usability improvements #4

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
There are some issues i found with treebeard:

- i would move the class methods in its own model-manager
- make the parent foreignkey mandatory so you can get rid of the add_root,
add_child and move functions that are not user friendly at all and don't
integrate well with the rest of django and its standard way of creating models.

Original issue reported on code.google.com by lauber.p...@gmail.com on 27 Nov 2008 at 3:02

GoogleCodeExporter commented 9 years ago 
What do you suggest? Trees are complicated beasts for a relational db, and even 
more
for a ORM.

Original comment by gpicon on 27 Nov 2008 at 9:10

GoogleCodeExporter commented 9 years ago

Original comment by gpicon on 12 Jan 2009 at 8:22

GoogleCodeExporter commented 9 years ago 
Closing as wontfix. The current API isn't perfect or very "djangonic", but it 
works pretty well with trees.

Please reopen if necessary with code examples on the proposal.

Original comment by gpicon on 14 Jun 2009 at 8:08