Return-Path: Mailing-List: contact torque-user-help@db.apache.org; run by ezmlm Delivered-To: mailing list torque-user@db.apache.org Received: (qmail 78512 invoked from network); 22 Mar 2003 17:21:02 -0000 Received: from www3.kc.aoindustries.com (209.15.201.111) by daedalus.apache.org with SMTP; 22 Mar 2003 17:21:02 -0000 Received: from ericemminger.com (163-44.9-67.se.rr.com [67.9.44.163] (may be forged)) (authenticated) by www3.kc.aoindustries.com (8.11.6/8.11.6) with ESMTP id h2MHL4B13598 for ; Sat, 22 Mar 2003 11:21:04 -0600 Message-ID: <3E7C9B7D.7010403@ericemminger.com> Date: Sat, 22 Mar 2003 12:21:01 -0500 From: Eric Emminger User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Turbine Torque Users List Subject: Re: generate data migration scripts References: <30462.147.154.235.53.1048282452.squirrel@stuff.hrnoc.net> <3E7BC935.2040502@kjinteractive.com> In-Reply-To: <3E7BC935.2040502@kjinteractive.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Phillip, Jim > 1. Query database 1 and store the results in XML > 2. Write an XSLT file to transform the XML results from database 1 into > XML valid for database 2 (depending on the differences between the two, > that may or may not be a lot of hand-coding). > 3. Transform the database 1 XML into database 2 XML > 4. Insert the new XML into database 2 I'm currently doing most of this. It seems like the best option so far. I use Castor to go between the database and XML. Step 4 does work! I also wrote a simple utility to generate a Castor mapping file from your Torque schema.xml file. I'd be happy to contribute it to Torque if you want it. Eric