Bug with simple tree structure #32
Comments
|
It means your tree structure contains a cycle. |
|
But it doesn't, it's just 3 Objects and one is the parent of another. The third has no relationship. |
|
Can you provide the stack trace
…On Sun, Jul 12, 2020, 15:36 Conrad ***@***.***> wrote:
But it doesn't, it's just 3 Objects and one is the parent of another. The
third has no relationship.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#32 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AARAEUL4OAVPGLPG4ZFHBSLR3I3FZANCNFSM4OT4CCXA>
.
|
|
Yeah sure: |
|
@heywbj Do you need anything else? |
|
@heywbj Do you have any take on why this is happening? |
|
Same problem here... |
|
Looks like the DRF implementation of get_initial leads to a recursive cycle if no initial data is provided. As a quick fix, you might be able to set the |
|
@LesPrimus 's solution worked for me. I can't think of a safe implementation that would allow recursive write permissions, so I think it'll be okay for now. Might this be related to issue #30 ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I implemented basically the exact recursive model and RecursiveModelSerializer and Django throws
maximum recursion depth exceeded while calling a Python objectwhich is interesting, because we only have one parent relation in the database with only 3 objects.is our serializer class and it doesn't work. I am using the latest Django 3.0.7 and DRF 3.11.0.
The text was updated successfully, but these errors were encountered: