Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 2 of 2 total |
DROP TRIGGER statement |
Wed, Feb 28 2007 12:40 PM | Permanent Link |
"Ole Willy Tuv" | 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 |
Thu, Mar 1 2007 4:50 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | 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 |
This web page was last updated on Sunday, May 19, 2024 at 08:46 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |