Skip to content

Conversation

@josevalim
Copy link
Member

No description provided.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we follow this change for the extras libraries? Since all of them use :rpc.call inside the query/3 function if I'm not mistaken.

%{columns: columns, rows: rows} = info_module.query(table_name, {repo, node}, opts)
# EctoMySQLExtras
case :rpc.call(node, repo, :query!, [query, [], query_opts]) do
  {:badrpc, {:EXIT, {:undef, _}}} ->
    raise "repository is not defined on remote node"

  {:badrpc, error} ->
    raise "cannot send query to remote node #{inspect(node)}. Reason: #{inspect(error)}"

  result ->
    result
end

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good to me!

@josevalim josevalim merged commit 20b9e71 into main May 19, 2025
4 checks passed
@josevalim
Copy link
Member Author

💚 💙 💜 💛 ❤️

@josevalim josevalim deleted the jv-use-erpc branch May 19, 2025 13:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants