embulk / embulk/embulk-input-jdbc
Full support for schema names
Open
- Dominant language
- Java
- Stars
- 106
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Description
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"`.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.