embulk-input-jdbc
embulk-input-jdbc copied to clipboard
Full support for schema names
SQL Server doesn't allow users to set schema search path per connection. PostgreSQL allows it but it is fragile because embulk-input-jdbc doesn't understand PostgreSQL's search order.
I think that all embulk-output-jdbc code should always specify table name with schema name. In other words, JdbcInputPlugin.buildSelectQuery
uses FROM "schema"."table"
rather than FROM "table"
.