You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
table!{
matches (id){
id -> Integer,
date -> Nullable<Date>,
time -> Nullable<Time>,
home_team_id -> Nullable<Integer>,
away_team_id -> Nullable<Integer>,
}}table!{
teams (id){
id -> Integer,
name -> Text,
}}joinable!(matches -> teams (home_team_id));joinable!(matches -> teams (away_team_id));
Have any workaround surfaced since this was opened?
This is the expected behavior. Otherwise we have no clue what you mean when you say matches.inner_join(teams). You can use the .on method to specify an explicit on clause.
Given the following two tables:
and
I want both relations to be joinable.
This is currently not possible because the joinable macro is generating a conflicting implementation of the trait JoinTo.
The text was updated successfully, but these errors were encountered: