Flexible solution for selecting translation for arbitrary connections

[tidyverse]

Flexible solution for selecting translation for arbitrary connections

@hadley commented on Oct 27, 2017, 7:46 PM UTC:

Alternatively could provide something like:

register_translation(class(con), "Oracle", identifier = "'", string = '"')

And have custom behaviour in sql_translate_env.default() that would call getS3method()

[muldan09]

Greetings!

I work on a team of analysts and this is the exact solution that we need in order to use dbplyr with our Oracle databases. The workarounds mentioned in other threads have not worked for us so this solution would be a lifesaver for us.

Is there an update on this proposed solution?

Cheers!

[hadley]

I've spent quite a bit of time thinking about how to do this, but I just can't come up with any approach that isn't going to a be lot of work. A large investment doesn't seem worth it to me, given that it only affects people who use RJDBC, that's now a pretty small audience given the amount of effort we've put into the odbc package.