dump - load

[Bart Pietercil]

Hi Ruslan,

taking over for a few days from Danny (the man insisted on vacation  
can you believe it :-))

On the subject:
I still believe it should be possible to export tables together with  
their trigger. I understand your reason (unique in db scope) however  
for us as developer it is important to be able to transfer a table  
(and the associated triggers) to another database without needing to  
dump the whole database (a pain when the db has over 100 tables) since  
LOGICALLY they are associated.
So I would plead for a 'with triggers' option when exporting a table

as always

tia

Bart Pietercil

On 13 Jun 2008, at 18:29, Ruslan Zasukhin wrote:

> On 6/13/08 4:27 PM, "Danny Lewkin" <daniel.lewkin at cognosis.be> wrote:
>
> Hi Danny,
>
>> But....
>>
>> it seems that triggers are NOT included in a table dump - load...
>> Is this normal? Triggers show op in schema editor as a 'table
>> element', so I would expect that they get dumped also...
>
> Yes, because Triggers belong to DATABASE scope.
>
> Triggers are shown as Table element, but you can note they are shown  
> also as
> DB element.
>
> And also note that you cannot have to triggers with the same name in  
> DB,
> right? This is the most important sign that triggers are DB Elements  
> first
> of all. As well as Links also.
>
> We show them as Table elements also just for comfort. Because this  
> also have
> big sense.
>
>
>
>
> -- 
> 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 mailing list
> Valentina at lists.macserve.net
> http://lists.macserve.net/mailman/listinfo/valentina