-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Error when including related table that does not have rows corresponding to the foreign key #28
Comments
I have been having the same issue. line 194 of dexie-relationships/dist/index.js is
I switched it to the following and it fixed the issue.
However i am not sure if this is the proper way of fixing the issue. |
@dfahlander Any input on this? Or your branch for #12? Would either be safe enough to use? |
mickyginger
added a commit
to mickyginger/fake-json-api
that referenced
this issue
Oct 2, 2019
Any update on this? I can make a PR for this if helpful |
mickyginger
added a commit
to mickyginger/dexie-relationships
that referenced
this issue
Oct 2, 2019
Merged
dfahlander
pushed a commit
that referenced
this issue
Oct 3, 2019
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Given the schema
If I add a band, but no corresponding album:
and then query the DB for bands, including albums by relation;
I´d expect to get one band with an empty array of albums, but instead I get the error
Is this the expected behaviour? Seems a bit odd that you cannot have 0 entities in a one to many relation.
The text was updated successfully, but these errors were encountered: