Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <329247748.345041266446367923.JavaMail.jira@brutus.apache.org>
Date: Wed, 17 Feb 2010 22:39:27 +0000 (UTC)
From: "Sylvain Leroux (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-4550) Using ij to copy data from one DB to
 an other
In-Reply-To: <2119585497.297391266319888052.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sylvain Leroux updated DERBY-4550:
----------------------------------

    Attachment: DERBY-4550_3.sql
                DERBY-4550_3.patch

Attaching the third version of this patch. The following statements now use qualifiedIdentifiers:
- PREPARE
- EXECUTE ... USING ...
- REMOVE
- GET CURSOR
- NEXT/PREVIOUS/FIRST/LAST/BEFORE FIRST/AFTER LAST/RELATIVE/ABSOLUTE/GETCURRENTROWNUMBER
- CLOSE

I added support for qualified identifiers on cursors as well, since I think it might be useful (as part of a different JIRA issue) to extend EXECUTE in order to accept cursors in the USING clause.

I add some tests at the end of ij7.sql. I wasn't able to add GETCURRENTROWNUMBER in the test suite since it writes directly on the output, and somehow, the test tool does not take that output into account. I filed a JIRA issue on this (DERBY-4553).

ToolScript test suite ran without any error.


> Using ij to copy data from one DB to an other
> ---------------------------------------------
>
>                 Key: DERBY-4550
>                 URL: https://issues.apache.org/jira/browse/DERBY-4550
>             Project: Derby
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Sylvain Leroux
>            Assignee: Sylvain Leroux
>            Priority: Minor
>         Attachments: DERBY-4550.diff, DERBY-4550.sql, DERBY-4550_2.diff, DERBY-4550_2.sql, DERBY-4550_3.patch, DERBY-4550_3.sql
>
>
> It is possible to have open connections to several databases while running ij, but it is not currently possible to copy data from one DB to an other one.
> Not only such a feature would allow to copy data between Derby databases. But, ij being mostly DB agnostic, if will ease import/export from any JDBC compliant data source.
> See http://old.nabble.com/Using-IJ-to-copy-data-from-one-DB-to-an-other-one-td27598138.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.