[
https://issues.apache.org/jira/browse/GEODE-6225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16739752#comment-16739752
]
Darrel Schneider commented on GEODE-6225:
-----------------------------------------
create jdbc-mapping now has --catalog and --schema options.
When using postgres if you created a schema and a table in it (using "create
table schemaName.tableName" syntax) then on the create jdbc-mapping you need to
use --schema=schemaName.
When using mysql if you created a schema and a table in it (using "create table
schemaName.tableName" syntax) then on the create jdbc-mapping you need to use
--catalog=schemaName. This is because mysql did not feel their "schemas" were
true schemas so they mapped them to the jdbc catalog instead of schema. The
--schema option should never be used with mysql.
> add support to create jdbc-mapping for catalog and schema
> ---------------------------------------------------------
>
> Key: GEODE-6225
> URL: https://issues.apache.org/jira/browse/GEODE-6225
> Project: Geode
> Issue Type: Improvement
> Components: docs, extensions
> Reporter: Darrel Schneider
> Assignee: Darrel Schneider
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The JDBC api support a catalog and schema option. Currently the JDBC
> connector always set these to null. The create jdbc-mapping should have
> options that allow users to specify non-default values for catalog and schema.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
