Database Adapter and Versions (postgrex, myxql, etc)
All
Current behavior
Today, we define several functions in Ecto.Adapters.SQL and we generate functions with docs inside the Ecto.Repo. This is a contrast to how Ecto.Repo works, which defines several callbacks in Ecto.Repo and lets the documentation tool tie them together.
Expected behavior
My suggestion is to introduce Ecto.SQLRepo which defines all relevant callbacks for the functions we generate, making them more consistent. The Ecto.Adapters.SQL API can then focus on custom adapter implementations.
There is no rush to implement this. I am documenting this for posteriority.
Elixir version
All
Database and Version
All
Ecto Versions
All
Database Adapter and Versions (postgrex, myxql, etc)
All
Current behavior
Today, we define several functions in
Ecto.Adapters.SQL
and we generate functions with docs inside theEcto.Repo
. This is a contrast to howEcto.Repo
works, which defines several callbacks inEcto.Repo
and lets the documentation tool tie them together.Expected behavior
My suggestion is to introduce
Ecto.SQLRepo
which defines all relevant callbacks for the functions we generate, making them more consistent. TheEcto.Adapters.SQL
API can then focus on custom adapter implementations.There is no rush to implement this. I am documenting this for posteriority.