does not appear in the trigger list. I'm sure it has been
stored by the
engine because when I try to create it again the "General error;-6013
POS(1) Duplicate trigger definition" message is returned. It
is strange
that I can't drop it with the "drop trigger
Jean-Michel OLTRA a écrit :
bonjour,
Le jeudi 26 août 2004, Xavier CAMIER a écrit...
Thank you for replying but as explained in the mail the trigger I
created appears nowhere and that's my problem.
Yes I did it and I'm wondering how it can be refused as it appears
nowhere at all
bonjour,
Le jeudi 26 août 2004, Xavier CAMIER a écrit...
> >>Thank you for replying but as explained in the mail the trigger I
> >>created appears nowhere and that's my problem.
> Yes I did it and I'm wondering how it can be refused as it appears
> nowhere at all :-(
Below is a message
Sven Köhler a écrit :
Thank you for replying but as explained in the mail the trigger I
created appears nowhere and that's my problem.
Have you upgraded the system-tables yet? Perhaps it helps. Just a guess.
Here is something I just found. When I drop the table and then recreate
it, the "hidden
Sven Köhler a écrit :
Thank you for replying but as explained in the mail the trigger I
created appears nowhere and that's my problem.
Have you upgraded the system-tables yet? Perhaps it helps. Just a guess.
Yes I did it and I'm wondering how it can be refused as it appears
nowhere at all :-(
Thank you for replying but as explained in the mail the trigger I
created appears nowhere and that's my problem.
Have you upgraded the system-tables yet? Perhaps it helps. Just a guess.
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:http://list
does not appear in the trigger list. I'm sure it has been
stored by the
engine because when I try to create it again the "General error;-6013
POS(1) Duplicate trigger definition" message is returned. It
is strange
that I can't drop it with the "drop trigger
om sql studio it
>does not appear in the trigger list. I'm sure it has been
>stored by the
>engine because when I try to create it again the "General error;-6013
>POS(1) Duplicate trigger definition" message is returned. It
>is strange
>that I can't dro
sure it has been stored by the
engine because when I try to create it again the "General error;-6013
POS(1) Duplicate trigger definition" message is returned. It is strange
that I can't drop it with the "drop trigger TRIG_MAINOEUVRESMAJPV of
COMPOSANTS" command. T
