Tim,

According to the ElevateDB SQL Manual, the DROP TRIGGER statement has no
deviation from the SQL:2003 standard.

AFAICS, the DROP TRIGGER statement in ElevateDB requires that a proprietary
FROM clause is specified:

DROP TRIGGER <Name> FROM <TableName>

The standard syntax is:

DROP TRIGGER <trigger name>

I'm not sure if this is an oversight or you really want to make the DROP
TRIGGER statement in ElevateDB incompatible with SQL ?

Ole Willy Tuv

Ole,

<< I'm not sure if this is an oversight or you really want to make the DROP
TRIGGER statement in ElevateDB incompatible with SQL ? >>

It's an oversight in the docs.  All table-level objects are uniquely named
within the scope of the table, not the schema, in EDB.

--
Tim Young
Elevate Software
www.elevatesoft.com