-
Notifications
You must be signed in to change notification settings - Fork 109
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
Issue with parent relations #60
Comments
Any PRs are welcome :) and yes package is still maintained. |
@psychonetic any progress on creating PR? I guess, best way to do this would be to detect self-referencing relationship and only use aliasing if detection returns true. |
@Kyslik I wasn't at home during weekend. We open a pull request today :) |
@Kyslik Thanks, you are fast :) I will check that out and will edit this answer here. |
@psychonetic yea, I pushed it to 5.4 now; not tagged yet; so you can install it using specific hash
Please do test and report here :) |
@Kyslik Yep, I already did. It's working perfectly! So you can tag it. |
Done ;), 5.4.6 Thanks for reporting the bug. |
First of all: great package!
I found an issue, if the model relates itself. Imagine you have a model Category, which references its parent category.
If you try to sort by parent.name or anything related to the parent category, it will fail, because both tables have the same name. But it can be fixed easily if one of the related tables would get an alias by default, when executing the join.
I may create a pull request.
By the way: Is the package still maintained?
The text was updated successfully, but these errors were encountered: