why

why

Hello,

I’m trying to dynamically pass a schema name into a function for use in a query. Can’t quite figure out in which format to pass in the schema name.

Pseudo code (not working):

def test(schema_name) do
  Test.Repo.all(from a in schema_name, where: a.name == "ACME")
end

Have tried various ways of passing the schema_name in, including in the form of a {“source”, Schema} tuple, as discussed here: https://stackoverflow.com/questions/40687186/how-can-you-dynamically-set-a-schema-table-name-for-a-ecto-model

But no luck so far… Any ideas how one could do this?

Thank you!

Showing Posts 1 to 6

1player

1player

What’s the error? Works for me, but used like you did gives you a error that says “queries that do not have a schema need to explicitly pass a :select clause in query”.

Also you might need the ^ operator in front of that constant "ACME" string.

Try this:

schema_name = "some_table"
Test.Repo.all(from a in schema_name, where: a.name == ^"ACME", select: a.id)

EDIT: by the way, do you mean Ecto schema (which is actually a table) or PostgreSQL schema (which is a different problem and answer altogether)? I assume it’s the former.

why

why OP

Yes, setting the variable inside the function works (for table names as well as for schema names). It’s also no problem to pass in a table name via the function head parameters.

My problem is passing in an Ecto schema name (not a table name) via the function head.

This works (inside the function):

schema_name = Account
Test.Repo.all(from a in schema_name, where: a.name == "ACME", select: a.id)

This I cannot get to work for a schema:

def test(schema_name) do
  Test.Repo.all(from a in schema_name, where: a.name == "ACME", select: a.id) 
end

P.S.: I don’t think one needs the pin before “ACME”, that seems to work fine as is also.

why

why OP

Btw, this is the error I get, when trying to pass the schema name in via function head parameter. My schema is called Account:

** (Protocol.UndefinedError) protocol Ecto.Queryable not implemented for Account of type Atom, the given module does not exist. This protocol is implemented for the following type(s): Tuple, BitString, Ecto.SubQuery, Ecto.Query, Atom

1player

1player

Ah, gotcha.

The use Ecto.Schema macro creates a __schema__ function that exposes some introspection details about your schema, and you can use that to find the actual table name as string (Ecto.Schema — Ecto v3.14.0)

def test(schema_name) when is_atom(schema_name) do
  # Get the table name as string
  table_name = schema_name.__schema__(:source)
  Test.Repo.all(from a in table_name, where: a.name == "ACME", select: a.id)
end

Hope this helps!

1player

1player

Sorry for the double post, but using the schema module actually works!

Your problem is using the Account atom, which isn’t probably aliased to its fully qualified name.

You’ll see that if you alias it, or use the fully qualified module name, such as YourApp.Data.Account, it will work.

alias YourApp.Data.Account

# Without the alias above, Ecto does not know what Account is. 
# You might have multiple Account modules in different namespaces.
test(Account)

# This will always work, alias or not
test(YourApp.Data.Account)
why

why OP

Awesome, thanks a lot, that fixed it, it was the aliasing :slightly_smiling_face:

Great help, really appreciate it!

— 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
kpanic
Hi everyone, I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding. I sta...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
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
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
ryanwinchester
apply_graft/2 doesn’t rewrite an add_many sub-workflow’s deps on an add step. Grafted jobs cancel with “upstream job was deleted” Version...
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

Elixir Forum

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews