I can import one canister’s Actor class into another canister, but it seems I can’t call any of that imported Actor’s functions from my Actor’s functions, even if they’re query functions themselves. Shouldn’t I be allowed to call query functions from other query functions, even if they live in diffe…

One would think, however, and as far as I understand, there is no guarantee that the other canister exists on the same subnet, and specifically if it doesn’t, then the subsequent query would need to go through XNet transfer. For now, your simplest solution would be to remove the query declaration f…

@enzo what do you mean by “query the database directory”? My “database” is just local data structures living on the Internet Computer, like if the src/database/main.mo actor contained a hash map member variable, for instance. Query functions are how I’m supposed to get data out of canisters when edi…

[image] mymikemiller: what do you mean by “query the database directly”? By database, I mean the Database actor that you defined in your code. Yes, the IC is orthogonality persistent and databases don’t really exist in the traditional scene. [image] mymikemiller: Query functions are how…

What’s the problem with XNet Transfer, then? Shouldn’t that work for my needs? Why wouldn’t that work for the query calls I’m trying to make? Because it would be slower due to having to transfer across the internet when it can’t all be done on one server? I’m ok with that. It would still be faster t…

Oh sorry! That’s a typo. I meant, query the database directly!

[image] mymikemiller: What’s the problem with XNet Transfer then? Will have to get back to you on the specifics, but my strong suspicion here is that the implementation is not optimized. My guess would be that they don’t do any message introspection to distinguish between updates and queries …

I solved this for my immediate needs by combining all my canisters into one so everything could communicate via fast query calls. Not ideal, obviously. Hopefully someone here has some info on when canisters will be able to communicate with each other without all the calls needing to be update calls…

That’s what I did too. Hope there will be a proper solution.

For Motoko, the rules can be summarized like this A user/frontend can call: a shared function (with consensus and state change), a shared query function (without consensus or state change). A class constructor can call: any local function. A shared function (or async expression) can call: a…

Can't call an imported Actor's query functions

Developers

claudio August 2, 2021, 8:39am 19

See here for a possible workaround in front-end applications.

Topic		Replies	Views
Query function with msg.caller? Developers	1	574	June 6, 2021
Shared function is only allowed as a public field of an actor Developers Functional-Programming	2	73	October 17, 2024
Calling/importing different actors in Motoko relationship Developers	7	1989	June 17, 2021
Simplest / best way to make inter-canister calls in Motoko Language Support Motoko	11	1724	February 9, 2025
Motoko Improvement: Module Actor Functions Language Support Motoko	8	375	April 24, 2024

Can't call an imported Actor's query functions

Related topics