We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Thank you for addressing this issue so quickly: #1101
Sadly, this rabbit hole might go a bit deeper. With the above fix, I immediately ran into the next possibly related thing:
Again, if I have two tables with a foreign key relationship between them, and I specify the relationship using a custom db_column_name, eg:
class FooTable(Table, tablename="foo", schema="public"): id = Varchar(length=20, primary_key=True, null=False) name = Varchar(length=64, unique=True, null=False) class BarTable(Table, tablename="bar", schema="public"): id = Varchar(length=20, primary_key=True, null=False) foo = ForeignKey(references=FooTable, null=False, db_column_name="foo_id")
Then when I try to query this relationship using prefetch:
bar = await BarTable.objects(BarTable.foo).where(BarTable.foo.id == "abc").first()
Then I get an error saying there is no matching column found.
If I leave out the prefetch, then it works without error, with the resulting dict containing the property:
"foo": "abc"
The text was updated successfully, but these errors were encountered:
It's probably another edge case we don't have a unit test for.
Hopefully it's a fairly easy fix again - making sure we use db_column_name instead of name in the query.
db_column_name
name
Sorry, something went wrong.
prefetch
ForeignKey
I've got a PR which fixes it - but needs some tests.
Successfully merging a pull request may close this issue.
Thank you for addressing this issue so quickly: #1101
Sadly, this rabbit hole might go a bit deeper. With the above fix, I immediately ran into the next possibly related thing:
Again, if I have two tables with a foreign key relationship between them, and I specify the relationship using a custom db_column_name, eg:
Then when I try to query this relationship using prefetch:
Then I get an error saying there is no matching column found.
If I leave out the prefetch, then it works without error, with the resulting dict containing the property:
The text was updated successfully, but these errors were encountered: