If a schema name begins with a number (or any strange character i assume), in_schema() throws a syntax error.
Please consider quoting the schema, table names by default in in_schema(), eg. by DBI::dbQuoteIdentifier().
Created on 2019-05-30 by the reprex package (v0.2.1.9000)
I think fixing this is going to be challenging, because we only know how to quote at SQL generation time, but in_schema() eagerly evaluates it's inputs. 🤔
I had issues connecting a schema on PostgreSQL until I realized PostgreSQL needs names to be quoted whenever some characters are upper case, and in_schema() doesn't do it by default.
It was a headache to debug but the fix was simply to use in_schema('"SCHEMA"', "table") rather than in_schema("SCHEMA", "table").
If it's tricky to implement, I think at least a note in the doc would go a long way.
If a schema name begins with a number (or any strange character i assume),
in_schema()
throws a syntax error.Please consider quoting the schema, table names by default in
in_schema()
, eg. byDBI::dbQuoteIdentifier()
.For example:
This doesn't connect and returns the trace below:
This connects:
The text was updated successfully, but these errors were encountered: