You are viewing a plain text version of this content. The canonical link for it is here.
Posted to torque-user@db.apache.org by Chris K Chew <ch...@fenetics.com> on 2003/02/20 19:40:46 UTC

RE: import/export with schema transformation

Two questions:

1.  Are you looking to do this from a turbine service, or as part of a build
process?
2.  Castor was mentioned the other day.  Did you look into it, and if so,
what has caused you to no longer consider it?  (just curious on this last
one)

I started a thread called 'Syncing the local DB from a remote DB' in
October.  Colin Chalmers mentioned that he had used torque, castor and
xml-rpc to sync remote databases.  You might be able to use some of his
ideas.

Chris

-----Original Message-----
From: Eric Emminger [mailto:eric@ericemminger.com]
Sent: Thursday, February 20, 2003 11:48 AM
To: Torque Users List
Subject: import/export with schema transformation


I'm trying to find an easy way to do the following.

1. import a data set into the database (e.g. from XML to PostgreSQL)
2. export a data set from the database (e.g. from PostgreSQL to XML)
3. transform the schema of a data set
3.1. rename columns/properties
3.2. convert a flat file into several related tables. Essentially, this
would normalize the data before import.

I know that Torque can export data with the datadump task and import
with the combination of the datasql and insert-sql tasks. However, I
haven't seen a solution to the transformation need.

Unless a solution already exists, I'm interested in adding this
functionality to Torque or whatever makes sense. Commons anyone?

I would greatly appreciate any feedback, ideas, etc.

Eric

--
Eric Emminger
eric@ericemminger.com


---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org


RE: import/export with schema transformation

Posted by Eric Emminger <er...@ericemminger.com>.
Chris

> 1.  Are you looking to do this from a turbine service, or as part of a build
> process?

Both! A build script would help when we set up new applications and
during testing. A service would be useful for our customers. So, we do
need both. At the least, a service could probably meet all our needs.

> 2.  Castor was mentioned the other day.  Did you look into it, and if so,
> what has caused you to no longer consider it?  (just curious on this last
> one)

Okay. Okay. :) I looked at Castor very briefly yesterday. I'm looking at
it with more detail now. It looks great so far! Thanks for prodding me.
:)

After a few minutes of digging, it looks like you use Castor XML
together with Castor JDO to accomplish these tasks. Very cool. It looks
elegant as well!!!

> I started a thread called 'Syncing the local DB from a remote DB' in
> October.  Colin Chalmers mentioned that he had used torque, castor and
> xml-rpc to sync remote databases.  You might be able to use some of his
> ideas.

Thanks for pointing this out. I'll start a new thread on this.

Eric

-- 
Eric Emminger
eric@ericemminger.com