Antoine Bolvy

A side note, I noted that even with hitting ^C twice, the background process wasn't killed / continued its happy life. I don't think this is something introduced by the...

So it would be true by default, setting it to false would toggle between use_stdio/nouse_stdio at the erlang options. Right?

Hey! Love this package :) I also have a relatively fast load time, but it's still the slowest of my packages: 

There's also this form ```elixir result = Ecto.Adapters.SQL.query!(MyRepo, "SELECT * FROM users", []) ``` But harder to deal with since the query is at the second position.

Works almost like a charm! Looking at the PR it seems like it's trying to look at popping arguments for this case: ```elixir Ecto.Adapters.SQL.query!(MyRepo, "SELECT * FROM users", []) ```...

(note, i'm only pointing it out because I thought your change was trying to handle that case, if that's not the case no worries, this must be a pain to...

For what it's worth, it appears to have not so much impact here, the app is still deployed ``` ubuntu@example:~$ mkdir test && cd test ubuntu@example:~/test$ touch .static ubuntu@example:~/test$ nano...

To be sure, I was talking about the business request entity, not Ecto's request :) I amended my first message to make it more explicit Regarding my example: A request...

>Using associations as query helpers is definitely an anti-pattern We indeed never write to this assoc, if this is what you mean. In that case well... we definitely overuse this...

>We recently added support to preload subqueries. Could you please point me to the documentation? Is it at the schema level, or when you give the preload options to a...