Skip to content
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

Support Laravel 6.0 #1

Merged
merged 29 commits into from
Sep 3, 2019
Merged

Support Laravel 6.0 #1

merged 29 commits into from
Sep 3, 2019

Conversation

mewebstudio
Copy link
Owner

No description provided.

SlyDeath and others added 29 commits May 16, 2017 14:11
When SQL error "key" is ambiguous
@getDuplicatesQuery used "id" directly as primary key for the model. Changed to "{keyName}" notation. :-)
…ndantOf with additional join(s)

If joins are made between the table using the NodeTrait and the table itself, using conditions whereDescendantOf or whereAncestorOf would throw an Integrity Constraint Violation error on columns _lft and/or _rgt.
Fix "ambiguous column" issue when using ancestor/descendant condition
Due to some changes in the Laravel internals in regard with handling
eager loading, upgrading the library to Laravel 5.7 is required. Also,
nobody should be on PHP < 7 anyway. So now is a good time, if any...
…zychaser#339, lazychaser#351, lazychaser#329, lazychaser#334, lazychaser#271)

The way eager loading is handled in Laravel has changed since the
original implementation of the NestedSet library. It was not possible
anymore to apply the scope to eagerly loaded ancestors/descendants
relationships.

Also removed defaultOrder() from the relations so custom orders can be
applied. Sorting should never be a part of a relation anyway, or it
would be hard to customize.
@mewebstudio mewebstudio merged commit 1c83c2e into master Sep 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants