-
Notifications
You must be signed in to change notification settings - Fork 356
Relation 1:N assumes foreign key is numeric during read conversion #1727
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
Comments
I attach simple project to reproduce |
Similar to this, i think: |
Please check if this issue is still present in the lates 3.2.x or 3.3.x releases. |
I think there's still an issue with relations; C.D[] is always empty on fetch. I'll try to make an integration test the next days. |
After local testing it looks like #1810 fixes my issue mentioned above. I'm pretty sure 3.3.x and 3.2.6 fixes this issue reported by @razubuddy. |
I have simple 1:N relation
Postgres schema looks like:
Test code:
Writing part works, but while reading from database it assumes foreign key
product
should be numeric:The text was updated successfully, but these errors were encountered: