[
https://issues.jboss.org/browse/TEIID-4760?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-4760:
----------------------------------
Description:
While importing, table (and other object) names are added to the schema with their
original names.
In our previous virtual database we imported two schema's that contain the same
objects but one is a production and another is a historical database.
We then change the name for e.g. table1 to prod_table1 or wh_table1 according to the
schema it came from. Some software that interacts with teiid can not distinguish between
different schemas and can not handle duplicate table names. So for this reason, this would
also come in handy.
It would come in handy if it is possible to add a prefix to names while importing
objects.
was:
While executing IMPORT FOREIGN SCHEMA, table (and other object) names are added to the
schema with their original names.
In our previous virtual database we imported two schema's that contain the same
objects but one is a production and another is a historical database.
We then change the name for e.g. table1 to prod_table1 or wh_table1 according to the
schema it came from. Some software that interacts with teiid can not distinguish between
different schemas and can not handle duplicate table names. So for this reason, this would
also come in handy.
It would come in handy if it is possible to add a prefix to names while importing
objects.
Summary: optional object name manipulations for import (was: optional object name
manipulations while executing IMPORT FOREIGN SCHEMA)
optional object name manipulations for import
---------------------------------------------
Key: TEIID-4760
URL:
https://issues.jboss.org/browse/TEIID-4760
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: Bram Gadeyne
Assignee: Steven Hawkins
Labels: ddl, import, import_wizard
Fix For: 10.3
While importing, table (and other object) names are added to the schema with their
original names.
In our previous virtual database we imported two schema's that contain the same
objects but one is a production and another is a historical database.
We then change the name for e.g. table1 to prod_table1 or wh_table1 according to the
schema it came from. Some software that interacts with teiid can not distinguish between
different schemas and can not handle duplicate table names. So for this reason, this would
also come in handy.
It would come in handy if it is possible to add a prefix to names while importing
objects.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)