What is this feature called in new Phoenix/Ecto?

sergio · June 2, 2022, 1:07am

We don’t see this in our Phoenix project, but I do see it in a new project I spun up to play with some tech.

What is that little arrow that tells me where the SQL query is originating from?

It seems very useful and I would like to include it in our project.

mindok · June 2, 2022, 1:14am

Looks like it was this PR in Ecto:

github.com/elixir-ecto/ecto

Optionally log last known call, publish stacktrace in telemetry

elixir-ecto:master ← v0idpwn:feat/log-last-known-call

opened 03:48PM - 13 Dec 21 UTC

v0idpwn

+194 -153

This PR is a response to https://github.com/elixir-ecto/ecto_sql/pull/363 and ht…tps://github.com/elixir-ecto/ecto_sql/pull/364. Ecto SQL PR: https://github.com/elixir-ecto/ecto_sql/pull/366 This is how logs will be displayed in Ecto SQL: ``` 17:41:01.272 [debug] QUERY OK source="my_schema" db=2.7ms queue=0.1ms idle=985.4ms DELETE FROM "my_schema" AS m0 [] ↳ EctoBug.reproduce/1, at: [file: 'lib/ecto_bug.ex', line: 6] 17:41:01.275 [debug] QUERY OK db=3.2ms idle=965.0ms INSERT INTO "my_schema" ("title","view_count") VALUES ($1,$2),($3,$4),($5,$6),($7,$8),($9,$10),($11,$12) ["sample", 1, "sample", 2, "sample", 3, "sample", 4, "sample", 5, "sample", 6] ↳ EctoBug.reproduce/1, at: [file: 'lib/ecto_bug.ex', line: 7] 17:41:01.277 [debug] QUERY OK source="my_schema" db=2.1ms idle=963.9ms SELECT m0."id", m0."title", m0."view_count" FROM "public"."my_schema" AS m0 [] ↳ EctoBug.reproduce/1, at: [file: 'lib/ecto_bug.ex', line: 16] # Note this one doesn't show the exact repo call but the function that calls the function that does the repo call. This is # due to underlying BEAM optimizations in tail calls 17:41:01.280 [debug] QUERY OK source="my_schema" db=2.5ms idle=955.0ms SELECT m0."id", m0."title", m0."view_count" FROM "public"."my_schema" AS m0 WHERE (m0."view_count" > $1) AND (m0."view_count" >= $2) [3, 2] ↳ TaskRunner.handle_info/2, at: [file: 'lib/ecto_bug/application.ex', line: 10] ``` To enable this feature, one would need to put in the repo options: ```elixir config :my_app, MyApp.Repo, get_stacktrace?: true ``` If enabled, the stacktrace also gets published in its entirety in respective telemetry events. This should probably only be enabled in dev environment due to performance impact.

Available in Ecto 3.8 onwards

sergio · June 2, 2022, 1:17am

Thanks! I’ll try updating our Ecto version so we get this niceness.

sergio · June 2, 2022, 1:25pm

I had to update Ecto in mix.exs:

{:ecto_sql, "~> 3.8"},

And modify my Repo config in dev.exs:

# Configure your database
config :gaming, Gaming.Repo,
  # snip
  stacktrace: true # <- Add this.