Dynamic schema name

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.

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.

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

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!

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)

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

Great help, really appreciate it!