Open KirillKayumov opened 3 weeks ago
Hi,
I think there is a chance we can do this. The main things I can think of that we'd need to be careful about:
json_extract_path
is agnostic between those types and we probably want to keep it that way.One more thing we should probably think about is dynamic paths.
Since the query bindings are compile-time constructs I don't think we can allow them in runtime evaluated paths unless we use dynamic
. We might want to evaluate how large a change that would be.
For example if it was prohibitively large then we'd need to decide if we want to allow bindings in compile-time paths only even though users would probably really want them in runtime paths.
Elixir version
1.16.2
Database and Version
PostgreSQL 14.9
Ecto Versions
ecto: 3.11.2, ecto_sql: 3.11.3
Database Adapter and Versions (postgrex, myxql, etc)
postgrex: 0.18.0
Current behavior
json_extract_path
or[]
variant doesn't support referencing columns from other tables. The Ecto query below fails to compile:Expected behavior
It would be very convenient if we could pass references to other columns in
json_extract_path
. I'm not sure about other DBs but for PostgreSQL I can see thatjson_extract_path
transforms to this SQL:Because it uses such syntax of array (as a '{}' string) it's clear why it doesn't work today. However, PostgreSQL supports another syntax where it's possible to reference columns:
I'm wondering if anything stops us from using the
array[]
syntax and allow referencing columns from other tables? If no, I can try to work on the fix.