AstonJ
Over the last few months, Ecto’s team has been working on some breaking changes to Ecto’s newest version.
In order to explain what changes are going to happen, José Valim is writing a series of blog posts. This is the first one.
The changes happened mostly on three areas:
- Split the Ecto repository apart
- Remove the previously deprecated Ecto datetime types in favor of the Calendar types that ship as part of Elixir
- Update to the latest JSON handling best practices
Where Next?
Trending in Discussions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Deploy Phoenix to your own VPS with PaaS ease: push-to-deploy, zero downtime, auto SSL, managed Postgres. 14-day free trial at potions.io
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
**Building the future of software with AI, trust, and human connection.**
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
PragTob
As one of the people in @michalmuskala’s ears about this change I’m super happy/ecstatic about the
ecto/ecto_sqlsplit. It reinforces that split for me it will help get ecto used for many more cases!Eiji
As lots of my private projects it’s still top secret, but I’m on way of planning to work on my own version of
ecto(after split). It will require one of libraries which I would like to release soon.dwahyudi
I don’t even know some people use
I don’t know any other ORM which has ability to do mapping to non-relational database.
ectofor storage other than relational database. I thought thatectois specific to relational database, no?So Ecto here is just the modelling itself?
While
ecto_sqlcontains migration and mapping between elixir code and sql?LostKobrakai
Ecto is also useful for mapping/validating user input into internal data structures. It’s not only useful if there’s actually a database at the end.
wmnnd
A typical example of using Ecto without a database would be processing a user-filled form, casting it into a struct and validating its contents.
AstonJ
There has been quite a bit of discussion on splitting Ecto in the past too
LostKobrakai
This also talks about using ecto differently at the user input ↔ elixir edge vs. elixir ↔ database.
dwahyudi
I thought about it as well.
What @OvermindDL1 said, sounds good.
I kinda wonder that such separation would be great for doing changeset validations on separate module.
In that validation module, we just use the validation library.
Decouple it with the model itself.
That way, I can unit-test the validation module easily.
But I don’t know if these validations will be used elsewhere other than the model themselves.
Btw, I almost confuse you with @LostKobrakai, your profile pictures look similar.
AstonJ
Haha yes they are quite similar - tho he is the better looking one
domvas
This is a very good news. And maybe I find the courage to not be lazy and find some fellows to develop a
ecto_cypheras the Neo4j-fanboy that I am (and because of the open cypher project)