dump - load

[Ruslan Zasukhin]

On 6/14/08 9:37 AM, "Bart Pietercil" <bart.pietercil at cognosis.be> wrote:

>> Hmm, no. Look.
>> 
>> Trigger of Table A can also do query on tableB.
>> Right?
>> 
>> And what todo ?
> 
> Well probably there are even more things that can go wrong, that is
> why I would leave it as an option (checkbox) in the export table
> command.
> I think this is a discussion on protecting a developer against himself
> (what you want to do) or empowering a developer (what I want) by
> letting him assume responsability.
> Importing a table with triggers that refer to a non (or not yet)
> existing table is the developers responsability and will lead to an
> error when creating the trigger. If the error reporting is good I
> don't see a problem with that.

Actually it is possible make
   
          pTrigger->get_UedTableCount()

And then we can export only Triggers that are based on this one table.



-- 
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]