I'm working on a project that utilizes the R2DBC library for reactive database access. However, I'm unsure if R2DBC supports the ApplicationIntent=ReadOnly parameter for SQL Server connections. This parameter is typically used in Microsoft SQL Server connection strings to indicate that the application intends to only read from the database, allowing SQL Server to redirect the connection to a read-only replica if available.
I've reviewed the official R2DBC documentation, but couldn't find any specific information about this parameter. I'm wondering if anyone has experience using R2DBC with SQL Server and can provide insights on whether R2DBC supports "ApplicationIntent=ReadOnly" or if there are any workarounds to achieve a similar behavior.
If R2DBC doesn't directly support this parameter, I'd appreciate suggestions on alternative approaches to ensure that R2DBC connections to SQL Server are treated as read-only, such as configuring the SQL Server connection at the database level.
Thanks to @AlwaysLearning, After exploring various options and searching for solutions, I took the initiative to edit the mssql-r2dbc sources.
I delved into the codebase, making the necessary modifications to incorporate the support for the "ApplicationIntent=ReadOnly" parameter in SQL Server connections.