Talk:Database trigger: Difference between revisions
m Signing comment by 201.155.6.245 - "→Postgresql does not support database level constraints: new section" |
|||
Line 33: | Line 33: | ||
== Postgresql does not support database level constraints == |
== Postgresql does not support database level constraints == |
||
Removed the part where it says: "PostgreSQL's database-level constraints may perform a similar function to a TRANSACTION COMMIT trigger, though they are oriented toward detecting and preventing disallowed conditions, not performing arbitrary operations." |
|||
Because PostgreSQL does not have database-level constraints (if it does, please add a reference |
Because PostgreSQL does not have database-level constraints (CREATE ASSERTION) (if it does, please add a reference that backups that claim). <span style="font-size: smaller;" class="autosigned">—Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[Special:Contributions/201.155.6.245|201.155.6.245]] ([[User talk:201.155.6.245|talk]]) 14:58, 31 March 2010 (UTC)</span><!-- Template:UnsignedIP --> <!--Autosigned by SineBot--> |
Revision as of 15:02, 31 March 2010
standards
Are triggers described by SQL93? What systems are compliant? Are these various features of various servers compliant or vendor extensions?
a musing
Imagine if a trigger was a method on an object.. When an object is modified, the trigger method is executed which then calls other objects and maintains invariants in the datastructure (garbage collection). Thus a trigger is nothing more than a precondition of a transaction to a database table (or an object).. However you like to look at it..
mutating table errors
We should add an explanation and an example for this problem. Additionally, it may be good to have some information on the behavior of different systems, i.e. can such errors occur or are they prevented. --Stolze 18:15, 19 November 2006 (UTC)
Microsoft SQL Server 'Inserted' and 'Deleted' Tables
After searching the internet for hours trying to figure out how to access data from the affected rows for conditional-trigger-logic, I stumbled upon MSDN's documentation of Inserted and Deleted tables, which store these values for the trigger incase it needs them. I added a small reference to these tables, but the comments I left could be worked over a little better.
I felt they were relevant here since it is mentioned that Triggers don't have parameters or arguments - thus the user should use the Inserted and Deleted tables for conditional-logic. —Preceding unsigned comment added by Sampsonvideos (talk • contribs) 19:24, 26 September 2007 (UTC)
No rollback of transactions via trigger?
According to the SQL documentation at least their server has the abilitiy to rollback transactions URL: http://msdn.microsoft.com/msdnmag/issues/03/12/DataPoints/ Can someone please check/clarify this? —Preceding unsigned comment added by 141.44.228.148 (talk) 15:08, 11 January 2008 (UTC)
Triggers in PostgreSQL
This section is a bit vague/confusing. You're left with the question so what triggers does PostgreSQL support? Lunchsure (talk) 20:27, 28 April 2008 (UTC) THATS —Preceding unsigned comment added by 81.28.124.159 (talk) 11:21, 1 November 2008 (UTC)
Postgresql does not support database level constraints
Removed the part where it says: "PostgreSQL's database-level constraints may perform a similar function to a TRANSACTION COMMIT trigger, though they are oriented toward detecting and preventing disallowed conditions, not performing arbitrary operations."
Because PostgreSQL does not have database-level constraints (CREATE ASSERTION) (if it does, please add a reference that backups that claim). —Preceding unsigned comment added by 201.155.6.245 (talk) 14:58, 31 March 2010 (UTC)