Jim Hester
Jim Hester
Are we sure we want this and not just better documentation on setting `options("connectionObserver" = NULL)`?
Yes this truncation is required by SQLServer limitations, it is unlikely to change. If you want these types of vendor specific behaviors I would suggest you use the vendor specific...
We are basically just returning with the driver and driver manager give us. I am not sure why they work like this, but here we are.
I guess this would imply a cassandra database would need it's own `dbWriteTable()` method, with an additional argument specifying the column(s) that are the primary key. Alternatively we just document...
That behavior was added in https://github.com/r-dbi/odbc/pull/313, @detule would likely be the best person to ask.
Could you try a different driver SQL driver, e.g. Microsoft's ODBC Driver for SuSE? (https://docs.microsoft.com/en-us/sql/connect/odbc/linux-mac/installing-the-microsoft-odbc-driver-for-sql-server?view=sql-server-ver15#suse17)
I would have to guess this is a freetds driver issue then, not knowing what else could cause this.
@detule adding that S4 method to odbc for FreeTDS seems worthwhile, as I imagine many people will be using older drivers for a while. Would you be interested in doing...
No, there is currently no support for specifying pre-connection attributes. Adding support for it would likely require a decent amount of work, it is unlikely to be done without an...
As mentioned in https://github.com/nanodbc/nanodbc/issues/215 we would have to modify nanodbc to support this, similar to what was done in pyodbc, and then expose an R interface for it in this...