ycv005
How to convert following Ecto Query into the Plain RAW SQL
%Workspace{name: "#{prefix() || "public"}"} |> Repo.insert()
Your response will be highly appreicable.
Trending in Questions
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
I’m aware of 2 such projects, are there others?
git: GitHub - team-alembic/realworld: A fullstack Phoenix LiveView application with back...
New
Hi all,
I’m working on a Phoenix project where I need to make external HTTP requests and I’m trying to choose between Req and HTTPoison....
New
How do I tell Hologram not to escape HTML when substituting into templates?
{Textile.render(@product.long_description)}
escapes the HTM...
New
Hi,
we run different LLM models across a cluster, with each node loading a configurable subset. Model-specific queues let nodes consume ...
New
Hello
I’ve been coding in Elixir for almost two years now because of my current job where we implemented Elixir in our application. But ...
New
Hi all, I’m new here and would like to hear peoples views on my Elixir/Phoenix based game-engine! :smiley:
Mutonex gamedesign was finish...
New
Other Trending Topics
Hey there,
I haven’t seen a list of useful Elixir specific skills for the popular AI tools yet so I’m starting one here with my first.
...
New
Hi everyone :waving_hand:
I wanted to share something I’ve been building — NowBlind, a random chat app designed to help people discover ...
New
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
Localize is the next generation localisation library for Elixir. Think of it as ex_cldr version 3.0. The first version will be released ...
New
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly)
AI dream has many faces, but general...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #code-sync
- #discussion
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #elixirconf-us
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #security
- #elixirconf-eu
- #api
- #forms
- #hex










Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
alexiss
regarding docs:
UPD sorry -
:insertis not supported (LostKobrakai
MyApp.Repo.to_sqlworks as well.alexiss
In Ecto 3.0 there are no
to_sqlcallback on repoLostKobrakai
Did you try it?
It’s documented here: ecto_sql/lib/ecto/adapters/sql.ex at 2ec71d74655cc076b6c965740a357dfe1505883a · elixir-ecto/ecto_sql · GitHub and here’s the macro, which adds it to the repo: ecto_sql/lib/ecto/adapters/sql.ex at 2ec71d74655cc076b6c965740a357dfe1505883a · elixir-ecto/ecto_sql · GitHub
It’s not part of the
Ecto.Repobehaviour though, which is why it’s not documented in that module. It’s only available if you’re using a SQL based adapter.ycv005
I want to query something like following
becuase I don’t want to use the schema in the command.
alexiss
In this case use query
hauleth
What are you trying to do exactly. Because I have strange feeling that we are dealing with XY problem.
LostKobrakai
It looks like you want to convert an ecto query to an sql query to use in migrations (hence the
execute). The problem here is that ecto actually cannot do that completely. Ecto as well as the underlying postgrex adapter does never interpolate parameters into the query. This is left to the database to do. So you’ll at best get the query with placeholders in the sql query and you’re left to replace those with actual values on your own. That’s whyto_sqlreturns a tuple of{query, parameters}.mxgrn
Do you mind sharing any pointers on how exactly Postgres does that interpolation for us? I just badly need a full plain SQL from a (complex) Ecto Query for performance analysis.
LostKobrakai
I don’t know what exactly happens behind the scenes, but I doubt the db does actually interpolate values:
Repo.explain(:all, query)