Part of the serverless effort we'll want to allow adding SQL server-side features that impact the type and format of the data presented to the clients. This has been achieved so far by gating these features on the (stack) versions. These however aren't granular enough and we'll need a new mechanism that is implemented by both the server and its clients.
Such a mechanism could be based on retrofitting the "version" request field (but in a BWC manner), adding a new dedicated field (for a features-version or some capabilities), or introducing serverless-compatible/dedicated clients.
Part of the serverless effort we'll want to allow adding SQL server-side features that impact the type and format of the data presented to the clients. This has been achieved so far by gating these features on the (stack) versions. These however aren't granular enough and we'll need a new mechanism that is implemented by both the server and its clients.
Such a mechanism could be based on retrofitting the "version" request field (but in a BWC manner), adding a new dedicated field (for a features-version or some capabilities), or introducing serverless-compatible/dedicated clients.
Related #102689