Question 1

How do I set up eql with rebar3 in an Erlang project?

Accepted Answer

Add eql as a dependency in rebar.config, then use eql:compile/1 to parse SQL files at runtime. The README shows compiling queries from a file path and accessing them via eql:get_query.

Question 2

eql vs sqerl: which is better for SQL in Erlang?

Accepted Answer

eql is better for teams wanting raw SQL in external files with simple parameterization, avoiding ORM complexity. sqerl is a SQL builder that programmatically constructs queries, which might suit more dynamic needs but adds abstraction.

Question 3

Can eql handle complex joins or transactions?

Accepted Answer

Yes, since eql uses raw SQL, you can write any SQL query including joins and transactions in the .sql files. However, transaction management must be handled separately in Erlang code with your database driver.

Question 4

Is eql secure against SQL injection?

Accepted Answer

eql uses parameterized queries with ? for positional parameters, which helps prevent injection. But named parameters like :table are unsanitized, so developers must manually sanitize inputs to avoid vulnerabilities.

Question 5

How to parse environment configs with eql?

Accepted Answer

Use the eql_config module included with eql, which parses structured files with sections, as demonstrated in the README for dev and prod environment settings.

Question 6

What databases does eql support?

Accepted Answer

eql is database-agnostic because it handles raw SQL strings, so it works with any database Erlang can connect to, such as PostgreSQL via pgsql or MySQL via emysql, as implied by the examples.

eql

What is eql?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions