Cruz
Hi,
I’d like to use Mnesia in a small prototype, but I don’t think I’m ready to deal with its Erlang API yet. So, I’m looking into the existing Elixir wrappers: Memento and ecto_mnesia. Any preference and/or opinions from people who have used them?
For the moment, I like that ecto_mnesia will allow me to switch DBs in the future if that becomes necessary. Anything else I should be aware of?
Thanks a lot
Where Next?
Trending in Discussions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Build Elixir applications with speed and confidence.
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
- #ai
- #elixirconf-us
- #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.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
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 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
Qqwy
We have been using
ecto_mnesiafor ~a year now and are currently in the process of switching to a different DB. This reasoning is correct and I suggest to do it, but be aware thatecto_mnesiais not a fault-free Ecto implementation. The main things we hit against were:Ecto.Streamsare not supported. There is an alternativeEctoMnesia.Table.Streambut it does not return Ecto structs but rather the underlying records for some reason.Ecto.Multiis supported, but errors raised (or rolled back) are not properly forwarded to the outer scope.And finally,
ecto_mnesiais configured in part itself, and in part by configuring:mnesia. Doing this properly is a bit finnicky.But especially for a small prototype, I’d say: Go for it!
Cruz
This is exactly the type of feedback I was looking for. Thank you!