CONCUR_READ_ONLY not supported for given type

[kothapraveen]

Hi,

Thanks for your prompt responses.

Currently facing below error, when we are working with Unix ODBC & FreeTDS.

CONCUR_READ_ONLY not supported for given resultset type TYPE_SCROLL_INSENSITIVE
but its working fine when the resultset type is TYPE_FORWARD_ONLY

Below are ResultSetTypes:
TYPE_FORWARD_ONLY
TYPE_SCROLL_INSENSITIVE
TYPE_SCROLL_SENSITIVE

Below are ResultSetConcurrency
CONCUR_READ_ONLY
CONCUR_UPDATABLE

[lurcher]

On 29/03/2024 16:44, kothapraveen wrote: Hi, Thanks for your prompt responses. Currently facing below error, when we are working with Unix ODBC & FreeTDS. CONCUR_READ_ONLY not supported for given resultset type TYPE_SCROLL_INSENSITIVE but its working fine when the resultset type is TYPE_FORWARD_ONLY Below are ResultSetTypes: TYPE_FORWARD_ONLY TYPE_SCROLL_INSENSITIVE TYPE_SCROLL_SENSITIVE Below are ResultSetConcurrency CONCUR_READ_ONLY CONCUR_UPDATABLE — Reply to this email directly, view it on GitHub <#166>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABYK62OV55KD3BR7XYKKN5LY2WK6VAVCNFSM6AAAAABFOU6TFKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIYTKNRXGY4DGMI>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

I may setup a auto responder that answers with "This is a FreeTDS issue, NOT unixODBC".

[kadler]

@lurcher Maybe a GitHub issue template that says the bug is probably in the driver, especially if the error message is something like [unixODBC][DRIVER] Something went wrong ...? Could also link to the issue trackers for various common ODBC drivers (maybe mark FreeTDS in bold, lol).

[v-chojas]

Try asking here: https://github.com/FreeTDS/freetds/issues