Hi Listmembers,

I played with the trigger of a basetable ssturm.ARTIKEL, but now I
run into trouble as shown below:

<------ BEGIN ------>

DROP TRIGGER UT_ARTIKEL OF ssturm.ARTIKEL
//
/*******************************************************************/
/* ---- Error -------------------------------                      */
/* Auto Commit: On, SQL Mode: Internal, Isolation Level: Committed */
/* General error;-4019 POS(14) Unknown trigger name:UT_ARTIKEL     */
/* DROP TRIGGER UT_ARTIKEL OF ssturm.ARTIKEL                       */
/*******************************************************************/
//
//
CREATE TRIGGER UT_ARTIKEL FOR ssturm.ARTIKEL AFTER UPDATE EXECUTE (
TRY
  IF NEW.LBESTAND < NEW.MBESTAND AND
     OLD.LBESTAND > NEW.MBESTAND AND
     NOT NEW.AARTIKEL
  THEN CALL ssturm.WARENBEDARF(:NEW.ARTIKELNUMMER, 0);
CATCH
  BEGIN
    SUBTRANS ROLLBACK;
    STOP ($RC, $ERRMSG);
  END;
)
)
//
/*******************************************************************/
/* ---- Error -------------------------------                      */
/* Auto Commit: On, SQL Mode: Internal, Isolation Level: Committed */
/*  General error;-6013 POS(1) Duplicate trigger definition        */
/*******************************************************************/
//
//
SELECT COUNT(*) FROM DOMAIN.TRIGGERS
//
/*******************************************************************/
/* +---+-------------+                                             */
/* |   | EXPRESSION1 |                                             */
/* +---+-------------+                                             */
/* | 1 |           0 |                                             */
/* +---+-------------+                                             */
/*******************************************************************/
//
//
SELECT * FROM DOMAIN.TABLES WHERE TABLENAME = 'ARTIKEL'
//
/*******************************************************************/
/* Schemaname......: SSTURM                                        */
/* Owner...........: MONA                                          */
/* Tablename.......: ARTIKEL                                       */
/* Privileges......: SEL+UPD-DEL+INS+REF+IND+ALT+                  */
/* Type............: TABLE                                         */
/* Tabletype.......: TABLE                                         */
/* Createdate......: 2005-08-23                                    */
/* Createtime......: 06:45:46                                      */
/* Updstatdate.....: 2005-09-06                                    */
/* Updstattime.....: 15:19:54                                      */
/* Alterdate.......: 2005-08-23                                    */
/* Altertime.......: 06:45:46                                      */
/* Unloaded........: NO                                            */
/* Sample_Percent..: ?                                             */
/* Sample_Rows.....: 20000                                         */
/* Comment.........: ?                                             */
/* TableID.........: 0000000000000439                              */
/* Dynamic.........: NO                                            */
/* Archive.........: NO                                            */
/* Variable_Columns: YES                                           */
/*******************************************************************/
//
//
SELECT * from domain.versions
//
/*******************************************************************/
/* Kernel.............: Kernel    7.6.00   Build 012-123-102-632   */
/* RuntimeEnvirionment: W32/INTEL 7.6.00   Build 012-123-102-632   */
/*******************************************************************/

<------ END ------>

The problem is that MaxDB states that there is no trigger I can
drop, but when I try to define one it states that the triggername
is duplicate!?

I tried it with an other triggername, but the result is the
same. This behaviour seems to be very equal as the problem
with public DB-functions.

What's wrong here?
Is it just bug No5 I found in 7.6?
Just to be sure: 7.6 has left the Beta-state?
I am wondering about this, as there are a lot of serious errors
(Length-Function, Public-Functions, Views & On Delete Restrict,
Create or replace view & schemas) that are not acceptable if
using MaxDB as a productive businesswide RDBMS. Looks like
a dark-green version of banana-software, so I would suggest to
work on a more effective testing-program before releasing new
versions in future ;)


What I did so far:
1) DBMGUI: Instance -> Configuration -> Upgrade System Tables
   Result: Done without problems

2) DBMGUI: Instance -> Check -> Database Structure ...
           -> Check DB Structure in Op-State ONLINE
           -> Extended
   Result: Checking of DB Structure succesfully finished

3) Stop Instance -> Reboot system -> Start instance
   Result: No problems

These steps did not solve the problem :(

Unfourtunately I do not have logfiles, as the instance is one of my private
paygrounds so I decide to overwrite the Logs without saving them.
I tried to define and drop triggers on other tables and this seems to work,
but the upper problem is still there. If someone needs more information from
me to track the bug/problem, please let me know and I will do my best to
provide more details on that issue.


Can someone help?


Thanks for help and comments!
Best regards

-- 
5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail
+++ GMX - die erste Adresse für Mail, Message, More +++

-- 
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to