David Frese

Same for the "ACE Editor" (https://ace.c9.io/), btw.

> Try this > > ``` > def ping(s) do > case query(s, 'PING') do > {:ok, _} -> {:ok, s} > {:error, err} -> {:disconnect, error!(err), s} > {:disconnect,...

Looks better, yes. Thank you! I also see this now ```elixir %DBConnection.ConnectionError{ message: ":closed", severity: :error, reason: :error } ``` and then later a simple ``` (RuntimeError) could not lookup...

Or maybe not, sorry. Tested again today (after fixing my App). And weirdly I now see this: ``` [error] Jamdb.Oracle (#PID) failed to connect: ** (DBConnection.ConnectionError) {:badarg, [{:erlang, :exit, [:undefined,...

Yes, that's gone. What (I think) I found out, though: - With the Postgresql adapter, the Ecto.Repo process does not exit. Accessing the db will just continue to raise a...

The repo process still exits; and I think still `:normal`. Also, it seems it exits the process calling the Repo function now, if already in 'disconnected' state. Postgres is: Repo...

That didn't change much. But I just dug my head into a bit, and noticed that a major difference to the Postgres adapter is, that it doesn't start an extra...

> Yes, I like it. > > type conn -> DBConnection.conn() - > GenServer.server() -> pid() | name() | {atom(), node()} So, conn must be pid of genserver also? >...

I wrote a test case, adding it to `jamdb_oracle_test.exs`. As the behaviour when the db is initially not available is the same as when the connection is lost on the...

Identical to me, or identical between the two branches? On the current master (501f45ccc977ba7757bc9827b5e6714c0c5675e8) I get ``` ........................................................................... 1) test DBConnection behaviour on connection errors (Jamdb.OracleTest) test/jamdb_oracle_test.exs:1231 ** (EXIT from...