Suggestion: Inform users about MySQL's View (virtual tables)? about eloquent-has-many-deep HOT 6 CLOSED

Is this a suggestion for this repository or the Laravel documentation?

from eloquent-has-many-deep.

Suggestion/Note in this repo to point out that MySQL's view is a possible solution /workaround for highly advanced relationships (with conditions, or unions etc)

While being able to work with eager loading

and then of course when Laravel's Migrations officially support creating MySQL Views + documentation then a lot of us would avoid this headache...

Did you get my reasoning to use MySQL's View?
If it doesn't make sense then it's alright just posting to possible save someone else's time

from eloquent-has-many-deep.

I really like the view idea, but I don't think it belongs in this repository.

What would be an example for a relationship with conditions?

from eloquent-has-many-deep.

You're right, its not for this repo but it is an alternative solution

Note that the key problem to solve is advanced/conditional deep relationships.

MySQL queries has no issues with this but eloquent wasn't built for it. (which this repo is trying to solve)

Example:

BillingAccount has many Orders
Order has many Coupons
Coupons has one Invoice
Invoice has many Payment

As you can see, a BillingAccount has Ordered some Coupons which has an Invoice that can be pending Payment or already paid in full (multiple Payments to cover single Invoice)

With MySQL view,
You can create 1 fake relationship pivot table for each relation in Laravel such that, you can get:

BillingAccount->paidCoupons()
BillingAccount->unpaidCoupons()

In total, 2 fake pivot tables

from eloquent-has-many-deep.

Using MySQL view as pivot table will also solve the Union problem mentioned in: #8

from eloquent-has-many-deep.

I've created a package for merging relationships using views:
https://github.com/staudenmeir/laravel-merged-relations

from eloquent-has-many-deep.