-
Notifications
You must be signed in to change notification settings - Fork 0
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
Compound foreign key support #2
Comments
Could this not be simplified to
Do we have a use case for an operator other than ==? |
I have not come across it yet where we need an operator other than ==. I thought about making it optional so that it can easily be changed if we need something else down the line. So in the above example the where would be constructed as follows:
|
yep. Might be worth compiling a list of all the relationship rules we need before implementing this so we know what functionality we will need |
The functionality to be able to string together multiple queries for the foreign key. At the moment there is only one
.where(...)
. Being able to have multiple.where(...).where(...)
(Note the firebase limits), would help the queries be more specific.The text was updated successfully, but these errors were encountered: