Valentine Studio v3.0.1 - copy Tables to another database

[Barry G. Sumpter]

Hi Ruslan

"But why copy to OTHER db ?"

Not exactly copying to another database but building a new one from the
dump.

Well for me, at the moment, this solves issues relating to VStudio,
convert_1_2, and my data.

As previously written, VStudio crashes repeatedly, when making structure
changes.
And the only way to import the XML structure changes with the data is to
create a new db on Load Dump.


hth

I think the term Load Dump is an oxymoron and needs to be changed to
"Re-Load Dumped DB".

Thanks,
    Barry G. Sumpter

-----Original Message-----
From: valentina-studio-bounces at lists.macserve.net
[mailto:valentina-studio-bounces at lists.macserve.net] On Behalf Of Ruslan
Zasukhin
Sent: Wednesday, 30 May 2007 8:59 PM
To: valentina-studio at lists.macserve.net
Subject: Re: Valentine Studio v3.0.1 - copy Tables to another database

On 30/5/07 1:43 PM, "Barry G. Sumpter" <BarrySum at BigPond.Net.AU> wrote:

> 1) Yes, one or many tables
> 
> 2)  Normalizing - Either moving a number of fields (1 to 100) from one
table
> to another (structure and/or data)
>      a) & b) - I need the structure AND the data

Ok, I see -- refactoring of db structure...

But why copy to OTHER db ?


-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]


_______________________________________________
Valentina-studio mailing list
Valentina-studio at lists.macserve.net
http://lists.macserve.net/mailman/listinfo/valentina-studio