Ecto: Model.get(id) instead of Repo.get(Model, id)
I'm just thinking if instead of using Repo.get(Game, id) it will be just Game.get(id) ? There are 9 functions. Actually have a module for that, but maybe this can be default behaviour with 'use Ecto.Model' ?
fazibear
>All comments
The whole point of Ecto is to not couple the Repository with the model. Once you start doing that, all goes downhill. Just call Repo.get/2, you may find it weird initially, specially coming from Rails, but it will really pay off in the long term.
Also, Please use the mailing list or StackOverflow for questions/help, where a wider community will be able to help you. We reserve the issues tracker for issues only.
josevalim
on 22 Aug 2015
👍5
Was this page helpful?
0 / 5 - 0 ratings
Related issues
sntran
路
4Comments
fuelen
路
3Comments
shahryarjb
路
3Comments
ericmj
路
3Comments
tverlaan
路
3Comments
Most helpful comment
The whole point of Ecto is to not couple the Repository with the model. Once you start doing that, all goes downhill. Just call
Repo.get/2, you may find it weird initially, specially coming from Rails, but it will really pay off in the long term.Also, Please use the mailing list or StackOverflow for questions/help, where a wider community will be able to help you. We reserve the issues tracker for issues only.