octosteve
commented
8 years ago I got this too! In the mean time, change your requirement in you mix.exs to {:postgrex, "0.10.0"}
Closed stochastic-thread closed 8 years ago
octosteve
commented
8 years ago I got this too! In the mean time, change your requirement in you mix.exs to {:postgrex, "0.10.0"}
mfeckie
commented
8 years ago Version that fixes this (currently) is {:postgrex, "0.10.0"}
stochastic-thread
commented
8 years ago dope, you guys are great. Guess the phoenix default config should be changed. Is 0.11 like a dev branch or something?
morenoh149
commented
8 years ago stochastic-thread
commented
8 years ago postgrex 0.10 works as desired, allows mix phoenix.server to start
postgrex 0.11 fails in the same way.
chrismccord
commented
8 years ago We need a new Ecto release with a bumped postgrex requirement. The fix for now is to pin postgrex at 0.10.0:
{:postgrex, "0.10.0"}Then run mix deps.update postgrex
// @josevalim
We'll have this taken care of soon. Thanks!
sorentwo
commented
8 years ago No, there isn't any Node style "odd numbers are experimental" versioning going on. There are just a lot of changes going into Ecto to prepare for 2.0, and Postgrex happens to be pre 1.0.
whito
commented
8 years ago Wow... thanks guys for being on top of this! :)
josevalim
commented
8 years ago Done. Ecto 1.1.2 is out with proper deps.
chrismccord
commented
8 years ago ❤️❤️❤️❤️❤️
Sent from my iPhone
On Jan 22, 2016, at 3:05 AM, José Valim notifications@github.com wrote:
Done. Ecto 1.1.2 is out with proper deps.
— Reply to this email directly or view it on GitHub.
princemaple
commented
8 years ago anyone still getting ecto 1.1.1 rather than 1.1.2 with default phoenix deps?
defp deps do
[{:phoenix, "~> 1.1.3"},
{:phoenix_ecto, "~> 2.0"},
{:postgrex, ">= 0.0.0"},
{:phoenix_html, "~> 2.3"},
{:phoenix_live_reload, "~> 1.0", only: :dev},
{:gettext, "~> 0.9"},
{:cowboy, "~> 1.0"}]
endThis, when mix deps.get, still gives me ecto 1.1.1 and postgrex 0.11.0, which don't fit together.
josevalim
commented
8 years ago "mix deps.update ecto" should fix it!
On Friday, January 22, 2016, Po Chen notifications@github.com wrote:
anyone still getting ecto 1.1.1 rather than 1.1.2 with default phoenix deps?
defp deps do [{:phoenix, "~> 1.1.3"}, {:phoenix_ecto, "~> 2.0"}, {:postgrex, ">= 0.0.0"}, {:phoenix_html, "~> 2.3"}, {:phoenix_live_reload, "~> 1.0", only: :dev}, {:gettext, "~> 0.9"}, {:cowboy, "~> 1.0"}] end
This, when mix deps.get, still gives me ecto 1.1.1 and postgrex 0.11.0, which don't fit together.
— Reply to this email directly or view it on GitHub https://github.com/phoenixframework/phoenix/issues/1489#issuecomment-173896803 .
José Valimwww.plataformatec.com.br http://www.plataformatec.com.br/Founder and Director of R&D
princemaple
commented
8 years ago @josevalim I forgot to mention that I removed mix.lock prior to running mix deps.get, and it still got me ecto 1.1.1, any ideas?
josevalim
commented
8 years ago It is fixed for good now then. :) Thanks for the report!
princemaple
commented
8 years ago @josevalim I can confirm that it's fixed now. Was the reason the 1.1.2 release didn't get picked up that the postgrex >= 0.0.0 was a main dependency and mix prioritized postgrex's version?
josevalim
commented
8 years ago Yes, exactly. it is completely ordering based. Shuffling the deps around would give ecto higher priority. :)
graeme-defty
commented
8 years ago This is all very nice, but would someone care to summarise for someone who does not yet quite grasp the magic incantations ... what do I actually have to DO?
My deps look like this:
defp deps do
[{:phoenix, "~> 1.1.4"},
{:postgrex, ">= 0.0.0"},
{:phoenix_ecto, "~> 2.0"},
{:phoenix_html, "~> 2.4"},
{:phoenix_live_reload, "~> 1.0", only: :dev},
{:gettext, "~> 0.9"},
{:comeonin, "~> 2.4"},
{:cowboy, "~> 1.0"}]
end
`
Sorry, I realise that doing mix deps.update ecto will fix the problem once, but how do I reorder my dependencies so that it does not go wrong next time?
... or is that it fixed for good?
Thanks
nubunto
commented
7 years ago ~Having trouble with this with Ecto 2.1.4, Elixir 1.4.4, and Postgrex 0.13.3~
My screwup. Multiple versions due to a umbrella app. Re-downloading everything solved it for me.
bigardone
commented
6 years ago Hi! Same issue here https://github.com/elixir-ecto/ecto/issues/1211#issuecomment-332648837
Hi, with a brand new Phoenix project I am experiencing an error where the app is unable to find the Ecto.Adapters.Postgres.Connection module. I was able to build and compile (and run) a Phoenix app yesterday so I suspect that this could be a transient issue but that seems very strange to me.
I tried to clean ecto and rebuild only that dependency but it did not solve the issue.
I am on Windows 10 so I suspect that's the issue but that doesn't solve the problem.
elixir-lang/ecto issue for reference: https://github.com/elixir-lang/ecto/issues/1211