Cruz
Ecto_mnesia or memento as an Mnesia wrapper?
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
Trending in Discussions
Other Trending Topics
Chat & Discussions>Discussions
Latest on Elixir Forum
Sponsor Spotlight
Producing high quality Elixir screencasts since 2017.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #performance
- #security
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.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Develop your skills with books, videos, and courses.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Most Liked
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!
Last Post!
Cruz
This is exactly the type of feedback I was looking for. Thank you!