You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Mamta A. Satoor (JIRA)" <ji...@apache.org> on 2013/06/25 06:03:20 UTC

[jira] [Updated] (DERBY-6219) Provide additional support for importing data via the optional foreignViews tool

     [ https://issues.apache.org/jira/browse/DERBY-6219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mamta A. Satoor updated DERBY-6219:
-----------------------------------

    Labels: derby_triage10_11  (was: )
    
> Provide additional support for importing data via the optional foreignViews tool
> --------------------------------------------------------------------------------
>
>                 Key: DERBY-6219
>                 URL: https://issues.apache.org/jira/browse/DERBY-6219
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Rick Hillegas
>              Labels: derby_triage10_11
>
> Once you have created views on a foreign database using the optional foreignViews tool (see DERBY-6022), you may need to import the data into your local schema. You confront various problems, including:
> 1) The need to order your inserts by foreign key dependencies.
> 2) The need to restart identity columns after the inserts.
> This issue is a place to track issues like this and brainstorm solutions.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira