itopiz
I have an interface in my schema:
interface :authentication_source do
field(:id, non_null(:id))
field(:name, non_null(:string))
field(:slug, non_null(:string))
field(:user_authentications, list_of(non_null(:user_authentication)))
resolve_type(fn
%OidcAuthenticationSource{}, _ -> :oidc_authentication_source
%MicrosoftAuthenticationSource{}, _ -> :microsoft_authentication_source
end)
end
as well as 2 nodes types that implement that interface:
node object(:oidc_authentication_source, id_fetcher: &authentication_source_id_fetcher/2) do
field(:name, non_null(:string))
field(:slug, non_null(:string))
field(:metadata_document, :string)
field(:client_id, :string)
field(:client_secret, :string)
field(:user_authentications, list_of(non_null(:user_authentication))) do
resolve(dataloader(Accounts))
end
interface(:authentication_source)
end
node object(:microsoft_authentication_source, id_fetcher: &authentication_source_id_fetcher/2) do
field(:name, non_null(:string))
field(:slug, non_null(:string))
field(:tenant_id, non_null(:string))
field(:client_id, non_null(:string))
field(:client_secret, non_null(:string))
field(:user_authentications, list_of(non_null(:user_authentication))) do
resolve(dataloader(Accounts))
end
interface(:authentication_source)
end
The Accounts source is using Dataloader.Ecto and when I run this GraphQL query:
query authenticationSources {
authenticationSources {
__typename
id
name
slug
... on OidcAuthenticationSource {
metadataDocument
clientId
clientSecret
}
... on MicrosoftAuthenticationSource {
tenantId
clientId
clientSecret
}
userAuthentications {
externalUserId
user {
id
email
displayName
}
}
}
}
I observe that 2 identical SQL queries are executed to load the :user_authentications:
- 1 query with all the IDs of the authentication sources of type
:oidc_authentication_source - 1 query with all the IDs of the authentication sources of type
:microsoft_authentication_source
The dataloader is very helpful but still it is triggering 1 SQL query per type implementing my interface.
I have re-read the following documentations but I cannot find a way to reduce this to a single query :
- Dataloader — absinthe v1.11.0
- Absinthe.Resolution.Helpers — absinthe v1.11.0
- Dataloader — dataloader v2.0.2
- Dataloader.Ecto — dataloader v2.0.2
Is it possible?
Trending in Questions
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
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
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
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
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
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
I’m new to elixir and just tried to install the elixirLS extension for VScode(ium) and it is throwing some errors that I would like help ...
New
Other Trending Topics
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
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
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
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
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
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
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #elixirconf-eu
- #metaprogramming
- #hex










Showing Posts 1 to 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
itopiz
I discovered that using a key function seems to do the trick:
Now a single SQL query is sent. The SQL query looks almost the same as before except it does not duplicate
authentication_source_dbidat the end ofSELECTand its does not useauthentication_source_dbidinORDER BY.This was not obvious from the documentation.
@benwilson512 Does that mean it is simply an undocumented feature or it is something that could disappear in future release? Could this behavior be added in the simpler form
resolve(dataloader(Accounts))as well?