Ignoring certain sources is a good feature, but if you just want to ignore oban_jobs, then it is not enough, as Oban also produces logs without source. And the issue is already solved, see Noisy with Oban · Issue #6 · fuelen/ecto_dev_logger · GitHub Probably you have to use Oban from main.
Happy to discuss solution for ULID.
fuelen
0
fuelen
fuelen
olivermt
This is friggin AMAZING!!!
I use datagrip and hate all the editing to test a logged query.
0
kasvith
BartOtten
This has been added to Ecto.
- [Ecto.Repo] Log human-readable UUIDs by using pre-dumped query parameters
Still eager to give this lib a try. Good work!
3
fuelen
v0.7.0 has been released 
I didn’t write here about previous tiny releases, but this one is notable by adding a Ecto.DevLogger.PrintableParameter protocol which allows printing yet not supported types and even user-defined postgrex types.
Also, it contains various small fixes.
1
fuelen
v0.11.0 has been released
This release adds a new option to setup which allows specifying custom function for query formatting.
An example of setup using pgFormatter utility:
defmodule MyApp.Application do
def start(_type, _args) do
Ecto.DevLogger.install(MyApp.Repo, before_inline_callback: &__MODULE__.format_sql_query/1)
end
def format_sql_query(query) do
case System.shell("echo $SQL_QUERY | pg_format -", env: [{"SQL_QUERY", query}], stderr_to_stdout: true) do
{formatted_query, 0} -> String.trim_trailing(formatted_query)
_ -> query
end
end
end
2
nallwhy
LostKobrakai
Ecto has no interpolation capabilities, which for a database library is a good thing. For querying a database interpolating parameters is not needed. That can and should always be done by the database to prevent sql injections. It however also means ecto can only give you the data it knows about, which are the sql for the prepared statements and separately all the parameters. That’s exactly what ecto supplies to the db as well.
It’s not as convenient to copy paste though, which is where an external library like this here can be useful.
1