Hi Mike,

To avoid confusion, we plan to include statements like USE and SET statements 
in the response as individual statements.

Yes, we can include the statement text to make the response clearer. One option 
is to introduce a new optional parameter that, when set to true, would include 
the full statement text. Alternatively, we could add a parameter that accepts a 
numeric value to specify how much of the statement text to include in the 
response.
I will also add a note about this potential enhancement in the APE for future 
reference.

Thanks,
Janhavi

From: Mike Carey <[email protected]>
Date: Tuesday, 15 April 2025 at 9:37 AM
To: [email protected] <[email protected]>
Subject: Re: [DISCUSS][APE] Proposal for Support Individual Responses for 
Multi-Statement Queries
I found myself wondering if it'd be useful to have some portion (a
prefix) of the statements in addition to statement IDs to help users
with correlating the inbound statements with the outbound responses?
(To deal with things like USE statements and SET statements - if they
are not going to be counted - and confusion that could result.  Maybe
include a discussion of the proposed treatment of those?)

On 4/11/25 10:33 AM, Suryaa Charan Shivakumar wrote:
> Hello Janhavi,
>
> This would be a useful feature to have. Here are some thoughts/suggestions,
> 1. (id: int) - can this be handled by the CC somewhere within asterixDB if
> multi-statement is enabled in request? Since we have a unique requestID we
> can assign random/sequential ID for statements I believe. This may help the
> queries look cleaner and not add changes to query parsing logic.
> 2. Not sure if this is intentional, in example 1 the statement ID inat
> response is not in-line with example 1 query.
> 3. Backward Compatibility - I'd suggest adding additional parameters in the
> request body like "multi-statement" and additional response objects without
> touching the existing API structure. Or using versioning for the API.
>
> Overall, it is a great feature to have. +1 to that!
>
> Best,
> Suryaa
>

Reply via email to