Ids gets mixed up with the previous table's ID about eloquent-has-many-deep HOT 7 CLOSED

This is an issue of the underlying HasManyThrough relationship and will be fixed in Laravel 5.8: laravel/framework#25812

Until then, you can use this workaround (only for lazy loading):

$address->address_with_billing_account()->getQuery()->get(['billing_accounts.*'])

from eloquent-has-many-deep.

Were my function parameters for hasManyDeep incorrect? It seems to work though

from eloquent-has-many-deep.

Please post the migrations of all three tables.

from eloquent-has-many-deep.

Address:

Account:

BillingAccount:

from eloquent-has-many-deep.

@staudenmeir

I manage to get around this problem earlier but this time it's causing other problems

Though this is a hasOneDeep(), I'd need it to return an array that why hasManyDeep() was used instead

from eloquent-has-many-deep.

@staudenmeir

To clarify the issue:

Eager loaded from hasManyDeep():

However, eager loaded ID for the BillingAccount is wrong:

BillingAccount Id should be 1, not 2.
2 is the Account's Id.

I discovered a pattern:

Those that has uses only primary keys id on top will cause this exact eager loading issue

It's possible there are id conflicts

from eloquent-has-many-deep.

@staudenmeir

Oops, just saw ur reply after posting.

Where is the suggested code supposed to be placed?
In the controller?

--EDIT:

turned it into an attribute and it worked! my.. the hours i spent on this 😭

    public function getAddressWithBillingAccountAttribute(){
        return $this->address_with_billing_account()->getQuery()->get(['crm_billing_accounts.*']);
    }

Thanks a lot!

This is an issue of the underlying HasManyThrough relationship and will be fixed in Laravel 5.8: laravel/framework#25812

Until then, you can use this workaround (only for lazy loading):

$address->address_with_billing_account()->getQuery()->get(['billing_accounts.*'])

from eloquent-has-many-deep.