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
I am struggling with a query whose parameters are being bind in the wrong order and I suspect it is a bug in Mariaex.
The query in question is: Prediction |> join(:inner, [p], m in Market, m.'UUID' == ^e.market_id and p.'IDMarket' == m.'IDMarket') |> Repo.update_all(set: [IDActivated: true])
and the resulting SQL statement is UPDATE tabPrediction AS t0 INNER JOIN tabMarket AS t1 ON (t1.UUID = ?) AND (t0.IDMarket = t1.IDMarket) SET t0.IDActivated = ? [true, "a5372405-173e-4b71-90e4-3c8a8e684134"]
Notice how true and the UUID are swapped.
Is this a bug or is it just me that I am not using ecto properly?
Thanks
The text was updated successfully, but these errors were encountered:
Hi,
I am struggling with a query whose parameters are being bind in the wrong order and I suspect it is a bug in Mariaex.
The query in question is:
Prediction |> join(:inner, [p], m in Market, m.'UUID' == ^e.market_id and p.'IDMarket' == m.'IDMarket') |> Repo.update_all(set: [IDActivated: true])
and the resulting SQL statement is
UPDATE tabPrediction AS t0 INNER JOIN tabMarket AS t1 ON (t1.UUID = ?) AND (t0.IDMarket = t1.IDMarket) SET t0.IDActivated = ? [true, "a5372405-173e-4b71-90e4-3c8a8e684134"]
Notice how
true
and the UUID are swapped.Is this a bug or is it just me that I am not using ecto properly?
Thanks
The text was updated successfully, but these errors were encountered: