-
Notifications
You must be signed in to change notification settings - Fork 462
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with get_children() method when using TreeManager. Wrong result. #689
Comments
I just found this bug exactly. model:
|
here is more logging with database queries |
Does it disappear after running |
@matthiask I did ran the rebuild after I post this, but I have the same results, so either my code is breaking the tree(which I think is unlikely because I get this error before updating anything on the tree), or there is a problem with the api when using the union from django. I'll investigate the queries and create a test afterwards if I can. |
after further investigation, I'm sure that the tree is ok and that the query being generated is wrong. Here are some more tests, where it is proved that only when there are union calls the code breaks.
I'm filtering name="R2" but those parameters never get to the query on the database level.
|
I have encountered an strange problem with the use of TreeManager
Here is my code:
When I test it. I get the following correct results:
But one child of the roots is unpublished and it does not show in the results. Here is the test:
I may not understand something, or I may have hit a bug??
Any ideas?
The text was updated successfully, but these errors were encountered: