Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (athena.apache.org: domain of bpendleton.derby@gmail.com
 designates 74.125.82.44 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=oHoubSQvqT7HPBCb/7c3saMbKPkfg7A4TvgRI/1V3IB4/SxEaj7eSdUvYX4Aq01Ndk
         ttGETijGtSz/LJOS7oKgvRqdsD3ZX2sxMtPS9uKeBZlDmBlRmlM9h1Kb5XK+dCeZpriv
         O7rY9Zf1FDJR59E0yRylM/g2mWN16mipFnXBk=
Message-ID: <4BD59EE6.7010206@gmail.com>
Date: Mon, 26 Apr 2010 07:10:46 -0700
From: Bryan Pendleton <bpendleton.derby@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: Derby Discussion <derby-user@db.apache.org>
Subject: Re: Transfer data between tables that are located in different
 databases
References: <100352.95620.qm@web59504.mail.ac4.yahoo.com>
 <alpine.DEB.1.00.1004260906030.11998@rocio>
In-Reply-To: <alpine.DEB.1.00.1004260906030.11998@rocio>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

>> As it is a lot of data that needs to be transferred between tables, the 
>> idea of using the system procedures to export the data from the source 
>> table, and then importing it in the target table appears to be good one. 
>> I will definitely give it a try, and will post the code here if I 
>> encounter any error.
> 
> How about in SQL:
> 
> INSERT INTO target SELECT * FROM source;

The tricky part is that the original poster wanted the source and target
tables to be in separate databases, which makes this solution impractical.

However, Derby 10.6's ij tool will contain a new feature DERBY-4550
https://issues.apache.org/jira/browse/DERBY-4550
which will enable uses such as this in the ij tool, I believe.

thanks,

bryan