Bug #10290 temp.table in trigger
Submitted: 1 May 2005 12:59 Modified: 18 Jul 2005 11:21
Reporter: Ties Meyer-Jark Email Updates:
Status: Closed Impact on me:
None 
Category:MaxDB Severity:S3 (Non-critical)
Version:7.5/7.6 OS:Windows (w2k)
Assigned to: Ulf Wendel CPU Architecture:Any

[1 May 2005 12:59] Ties Meyer-Jark
Description:
If creating a trigger with a "create temp.table" in it, it wil be successfully accepted but not listed in domain.triggers.
It cannot be dropped and no other trigger for the table can be created because a  duplicate trigger is mentioned by the db.

How to repeat:
Just create trigger with "create temp.table" in it.

Suggested fix:
put the temp.table stuff into a dbproc and call it from the trigger.
[2 May 2005 13:10] Ulf Wendel
How to verify:

create table t1(col char(2))
//
create trigger trig1 for t1 after update execute (
  try 
    create table temp.foo (bar char(2));
  catch 
    if $rc <> 100 then stop ($rc, 'unexpected error');
  )
//
drop trigger trig1 of t1
[9 May 2005 20:05] Ulf Wendel
Ahoy!

We're working on a patch. You can check the progress of this on www.sapdb.org/webpts. Use the Advanced Search to check for issue 1135396 . Please do this on your own. I can't promise a release date at the moment.

Best regards,
Ulf
[18 Jul 2005 11:21] Ulf Wendel
Reported
	

Settlement
	

Delivered
	  	
	7.6.00.05 	Delivered 	7.6.00.12 	  	
	

Created
	

Processed
	

Completed
	

Affected OS
	
	2005-05-04 	2005-05-12 	2005-05-12 	All