Use exported odbc classes

[hadley]

The dev version of odbc exports the classes it defines, so once it's on CRAN you can use them, rather than redefining yourself (

DatabaseConnector/R/DBI.R

Lines 61 to 70 in bee58a3

	class_cache <- new.env(parent = emptyenv())
	# Simple class prototype to avoid messages about unknown classes from setMethod
	setClass("Microsoft SQL Server", where = class_cache)
	setClass("DatabaseConnectorConnection", where = class_cache)
	setClass("DatabaseConnectorJdbcConnection", where = class_cache)
	setClass("DatabaseConnectorDbiConnection", where = class_cache)

). This will avoid conflicting classes definition between odbc and DatabaseConnector.

[schuemie]

Thanks! I think this fits nicely with our new development to use dbplyr backends for the various data platforms @ablack3