Fl4m3Ph03n1x

Fl4m3Ph03n1x

Background

I have a a couple of queries that result in the archival of some metadata items. My objective is to merge these queries into one (if possible).

Code

meta_item_ids_to_archive =
      Post
      |> where([post], post.archive_meta)
      |> select([post], %{item_id: post.meta_id})
      |> subquery()

archive_meta_items_query =
      Meta
      |> join(:inner, [item], item_to_archive in ^meta_item_ids_to_archive,
        on: item.id == item_to_archive.item_id
      )

########
later on
########

Multi.update_all(
  :query_a, 
  archive_meta_items_query, 
  set: [archived: true]
)

So my original query starts with Post and then int eh subsequent query I start with Meta. I want to archive items in the Meta table. My first attempt at merging these queries was the following:


new_query = 
  Post
  |> where([post], post.archive_meta)
  |> join(:inner, [post], item_to_archive in Meta,
        on: post.meta_id == item_to_archive.item_id
  )

Multi.update_all(
  :query_a, 
  new_query, 
  set: [archived: true]
)

Problem

Now, the issue here is that this won’t work:

field archived in update does not exist in schema Post in query (…):

Because my new_query starts with Post instead of Meta, the update operation fails.

Question

  • Is there a way to tell Ecto “I want the Meta table returned instead of Post?”
  • If now, how can I solve this?

Showing Posts 1 to 4

LostKobrakai

LostKobrakai

I’d suggest making use of Repo.to_sql(:update_all, query) and seeing what ecto generates. With SQL you can only update rows in a single table, so that table name needs to show up in th correct place. With ecto that will be the table name of the first binding in the query.

Fl4m3Ph03n1x

Fl4m3Ph03n1x OP

And I can’t change the first binding? What I understand here is that no matter what I will always need 2 queries.
I was wondering if using subquery() would allow me to cheat.

LostKobrakai

LostKobrakai

I don’t think you need a subquery. A plain join might be enough. Though those questions indicate even more that it might be worthwhile investing into learning more about sql – this will in turn make it easier to create queries with ecto as well.

Looking at things just from the ecto perspective can be deceiving, as “code” is usually much more flexible than a declarative sql query.

al2o3cr

al2o3cr

The first approach that comes to mind is to reverse the join - since it’s an INNER, either form will return the same rows:

new_query = 
  Meta
  |> join(:inner, [meta], post in Post,
        on: post.meta_id == meta.item_id.
        on: post.archive_meta
  )

Multi.update_all(
  :query_a, 
  new_query, 
  set: [archived: true]
)
— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
RemyXRenard
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
asweet-confluent
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New

Other Trending Topics Top

JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New

Latest on Elixir Forum

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews