Geek Answers Handbook

Using Phoenix Framework without Ecto

I am developing a web-based application supported by Phoenix, and I am exploring alternative storage methods for the current SQLite (and its Ecto driver) (yes, I heard about PGSQL, no, I don't want to use it.)

I would like to use LevelDB and H2LevelDB, which has an Erlang driver available on Github

However, at compile time, I realize that Phoenix seems to rely a lot on Ecto, even in modules charged by rendering eex templates. Which I find a little scary, a little strange and a little annoying at the same time. So, would it be safe to blindly clear all links to Ecto from pre-generated files, or should I switch to something else for my web interface?

+5
source share
1 answer

Phoenix does not rely on ecto. Can be used successfully without the other. Integration is performed through a couple of protocols that are implemented in the phoenix_ecto package.

The phoenix generator will create an application with ecto by default - the reason is to give the user something "with the batteries turned on." You can easily remove this by passing the --no-ecto flag to the --no-ecto generator.

+14
source

More articles:


All Articles