Open thinh-ngu opened 2 months ago
I figured out that when using "set-session-context": true that you have to add Pooling=False at the end of your connection string.
DATABASE_CONNECTION_STRING='Server=****;Database=****;TrustServerCertificate=true;Pooling=False;
If there is an alternative solution to this , please let me know.
Could we do either any of the following as enhancement?
What happened?
When requesting for multiple api requests when session context is "set-session-context": true. This is for using DB Type: DWSQL for using against Fabric SQL endpoints.
It causes the following api response:
{ "error": { "code": "DatabaseOperationFailed", "message": "Cannot set key 'aud' in the session context. The key has been set as read_only for this session.", "status": 500 } }
I am assuming the session is being sticky and not starting new sessions for each call. For some reason it may be caching the session when "set-session-context": true, but from my understanding that should default to false.
Version
0.11.130
What database are you using?
Azure SQL
What hosting model are you using?
Container Apps
Which API approach are you accessing DAB through?
REST
Relevant log output
Code of Conduct