We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
DON'T CONFUSE WITH MANY-TO-MANY!
https://hexdocs.pm/ecto/Ecto.Schema.html#belongs_to/3-polymorphic-associations
In Ecto, we have three ways to solve this issue. The simplest is to define multiple fields in the Comment schema, one for each association: * task_id * post_id Unless you have dozens of columns, this is simpler for the developer, more DB friendly and more efficient in all aspects.
In Ecto, we have three ways to solve this issue. The simplest is to define multiple fields in the Comment schema, one for each association:
* task_id * post_id
Unless you have dozens of columns, this is simpler for the developer, more DB friendly and more efficient in all aspects.
Is my assumption correct that here schema is used interchangeably with the repo (i.e., the database schema)?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Uh oh!
There was an error while loading. Please reload this page.
DON'T CONFUSE WITH MANY-TO-MANY!
https://hexdocs.pm/ecto/Ecto.Schema.html#belongs_to/3-polymorphic-associations
Is my assumption correct that here schema is used interchangeably with the repo (i.e., the database schema)?
The text was updated successfully, but these errors were encountered: