Mailing-List: contact torque-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Torque Users List" <torque-user@db.apache.org>
Message-ID: <002601c41e4d$ee94f0f0$690ba8c0@int.globaltechbg.com>
From: "Bogdan Vatkov" <bvatkov@globaltech-bg.com>
To: "Apache Torque Users List" <torque-user@db.apache.org>
References: <CDEPKAKGODNNBOPLIIOCMEKFCDAA.danihuan@cisco.com>
Subject: Re: using torgue to manage production schema change
Date: Fri, 9 Apr 2004 19:15:53 +0300
Organization: Global Communications Technologies
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Yes Daniel,
That is right.

regards,
bogdan
----- Original Message -----
From: "Daniel Huang" <danihuan@cisco.com>
To: "Apache Torque Users List" <torque-user@db.apache.org>
Sent: Friday, April 09, 2004 7:05 PM
Subject: RE: using torgue to manage production schema change


> Hi Bogdan,
>
> Thanks for the advice.
>
> As a matter of fact, I do have 1G of RAM, and datadump target runs just
> fine. But datasql target runs forever. Therefore I am using the native
> dump/restore tool now (imp/exp for Oracle, to be specific).
>
> However, the point of my original post was, for a production database, I
> believe generating alter table statement is the best solution. And I
really
> would like to recommend this as an enhancement to future torque releases.
>
> Thanks
> Daniel
>
> -----Original Message-----
> From: Bogdan Vatkov [mailto:bvatkov@globaltech-bg.com]
> Sent: Friday, April 09, 2004 8:57 AM
> To: Apache Torque Users List
> Subject: Re: using torgue to manage production schema change
>
> Hi,
> I recommend you to use native (console ) tools for
> dump/restore the data (not the structure of the database)
>
> XML oriented one is not a good idea. (or at least unless you have 1-2 GB
> RAM)
> regards,
> bogdan
> ----- Original Message -----
> From: "Daniel Huang" <danihuan@cisco.com>
> To: "Apache Torque Users List" <torque-user@db.apache.org>
> Sent: Friday, April 09, 2004 6:53 PM
> Subject: RE: using torgue to manage production schema change
>
>
> > Hi Thomas,
> >
> > May I ask how big your project-data.xml is? Mine is 1.6M and datasql
> target
> > runs forever. Not really a feasible solution for me.
> >
> > Besides, production data will keep growing, until some day it will
become
> to
> > big for datadump target.
> >
> > Thanks
> > Daniel
> >
> > -----Original Message-----
> > From: Thomas Edwin Santosa [mailto:katalis@telkom.net]
> > Sent: Thursday, April 08, 2004 11:57 PM
> > To: Apache Torque Users List
> > Subject: Re: using torgue to manage production schema change
> >
> > On Friday 09 April 2004 05:47, Daniel Huang wrote:
> > > Hi,
> > >
> > > Currently under torgen-gen 3.1, if you run
> > > ant -f build-torque.xml sql
> > >
> > > It will generate sql statements that drop tables and create new ones.
> This
> > > works great for development work. However, in a production
environment,
> > > this is not feasible because it will just drop all data as well.
> > >
> > > It will be great if the ant sql target will be able to generate alter
> > table
> > > statements so that it is safe to apply the generated DDL to a
production
> > > environment.
> > >
> > > Does this sound like a good enhancement idea for future releases?
> > I myself managed to do that using datadump sql datasql and insert-sql
> > target.
> >
> > Thomas
> > >
> > > Thanks
> > > Daniel
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> > > For additional commands, e-mail: torque-user-help@db.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> > For additional commands, e-mail: torque-user-help@db.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> > For additional commands, e-mail: torque-user-help@db.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-user-help@db.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-user-help@db.apache.org
>


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