Phoebe Goldman

Also move the `/v1/database/:name/procedure/:func` route under the `unstable` path component, unless #3659 is already done.

@aasoni some time after moving it under `unstable`, we intend to remove the separate procedure route in favor of making `/v1/database/:name/call/:func` able to transparently invoke both reducers and procedures.

> would you explain what would change from the client SDKs perspective? It's not super clear to me why we would need to change the client SDKs, I'm thinking this...

I'd like to prioritize this relatively highly, because it will eliminate the recurring pattern of BitCraft asking for some weirdly specific callback that they need for an individual feature.

We like the former version, where the same `call` CLI command can do either. We intend to modify the `/v1/database/:name/call/:func` route to call either reducers or procedures, at which point...

Desirable because procedures return `SpacetimeType` values, and we'd like users to be able to return `Result` for error-handling.

I manually caused an error using the following diff: ```diff modified crates/durability/src/imp/local.rs @@ -195,6 +195,14 @@ impl

> > I'm observing (Rust SDK) clients not being disconnected promptly > > Ok, so it looks like reducer calls are accepted indefinitely, even if the connection is closed. This...

We nuked the `query!` macro.

I think this is higher priority than the [C#](https://github.com/clockworklabs/SpacetimeDB/issues/3060) and [TypeScript](https://github.com/clockworklabs/SpacetimeDB/issues/3030) tickets since the Rust client SDK re-uses a single `ConnectionId` throughout the whole process, whereas the other two SDKs...