In addition to that, I struggled to find a well maintained library similarly to Devise. Also, many people won’t agree to me, but Ecto is also a kind of pain. I think Phoenix would have been in a better position if there were libraries like ActiveRecord and Devise.
subbu|4 years ago
Once your database becomes sufficiently complex you start writing a lot more sql.
ActiveRecord's way of chaining scopes to combine multiple scopes is brittle. You can't customize the conditions. Ecto solves this by giving you composability. You can build on top of your earlier commands. If you combine this with pattern matching in the functions or Enum.reduce you have an extremely powerful and a flexible query engine.
Ecto also relies on the strengths of underlying database engine rather than treating it as a black box. If you are dealing with 100s of tables Rails way of polymorphic design doesn't give you referential integrity. I like Ecto's recommendations: https://hexdocs.pm/ecto/polymorphic-associations-with-many-t...
hnedeotes|4 years ago
cpursley|4 years ago
pmarino90|4 years ago
https://dashbit.co/blog/a-new-authentication-solution-for-ph...
dasil003|4 years ago
brightball|4 years ago
yoneyone|4 years ago
cultofmetatron|4 years ago
That said, the community is moving towards phx_gen_auth which jose himself wrote and will come out of the box with 1.6