Timeline for SQL Trigger to verify account, if not verified dont process stored procedure/transactions
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 21, 2012 at 18:41 | vote | accept | Patriotec | ||
| Jun 19, 2012 at 12:43 | answer | added | RBarryYoung | timeline score: 3 | |
| Jun 18, 2012 at 15:15 | answer | added | Simon Hughes | timeline score: 1 | |
| Jun 18, 2012 at 14:30 | history | edited | Patriotec | CC BY-SA 3.0 |
added 847 characters in body
|
| Jun 18, 2012 at 13:36 | comment | added | Jānis | ooo, by "trigger" you mean not table trigger but some event that is triggered before procedure call.. Well.. you can wrap procedure in another procedure, that does verification. And there must be good reason why you do this verification otherwise than through standard user permissions.. | |
| Jun 18, 2012 at 13:21 | history | migrated | from stackoverflow.com (revisions) | ||
| Jun 18, 2012 at 13:21 | comment | added | Thomas Stringer | @Jānis And how would he fire a trigger prior to stored proc execution? | |
| Jun 18, 2012 at 12:59 | comment | added | Jānis | just verify (whatever you mean by that) user in trigger before procedure call. Where is problem exactly? | |
| Jun 18, 2012 at 12:38 | comment | added | Thomas Stringer | I'm with @Damien_The_Unbeliever, this should be handled with permissions. | |
| Jun 18, 2012 at 12:38 | comment | added | marc_s |
In a trigger (AFTER INSERT ?) you could just simply roll back the running transaction to undo any inserts, if your criteria is not satisfied
|
|
| Jun 18, 2012 at 12:26 | comment | added | Damien_The_Unbeliever | Why is the permissions system inadequate for the task? | |
| Jun 18, 2012 at 12:18 | history | asked | Patriotec | CC BY-SA 3.0 |