Defensive Database Programming - Red Gate Software

More documents

Recommendations

Info

Chapter 4: When Upgrading Breaks CodeVALUES ( 1 ,'Road Construction on Rt 59' ,'Lynn Lewis' ,0) ;Listing 4-22: The FrontPageArticles table, with test data.The MERGE command shown in Listing 4-23 will update the existing article and inserta new one.MERGE dbo.FrontPageArticles AS targetUSING( SELECT 1 AS ArticleID ,'Road Construction on Rt 53' AS TitleUNION ALLSELECT 2 AS ArticleID ,'Residents are reaching out' AS Title) AS source ( ArticleID, Title )ON ( target.ArticleID = source.ArticleID )WHEN MATCHEDTHEN UPDATESET Title = source.TitleWHEN NOT MATCHEDTHEN INSERT(ArticleID ,Title ,NumberOfViews)VALUES ( source.ArticleID ,source.Title ,0) ;SELECT ArticleID ,Title ,NumberOfViews124
Chapter 4: When Upgrading Breaks CodeFROM dbo.FrontPageArticles ;ArticleID Title NumberOfViews----------- ------------------------------ -------------1 Road Construction on Rt 53 02 Residents are reaching out 0Listing 4-23: Demonstrating the MERGE command (SQL 2008 and upwards).Issues When Triggers Using @@ROWCOUNT AreFired by MERGEThe MERGE statement is a powerful new feature but, again, we need to be mindful ofits use alongside existing code. In this example, I will demonstrate how a previouslyworking trigger may start to misbehave when called from a MERGE statement.Consider the trigger shown in Listing 4-24, designed to prevent the deletion of morethan one row at a time from the FrontPageArticles table.CREATE TRIGGER CannotDeleteMoreThanOneArticleON dbo.FrontPageArticlesFOR DELETEASBEGIN ;IF @@ROWCOUNT > 1BEGIN ;RAISERROR ( 'Cannot Delete More Than OneRow', 16, 1 ) ;END ;END ;Listing 4-24: Creating the CannotDeleteMoreThanOneRow trigger.We can test out our trigger using the code shown in Listing 4-25.125
Page 5 and 6:
Chapter 2: Code Vulnerabilities due
Page 7 and 8:
Enforcing Data Integrity in the App
Page 9 and 10:
About the AuthorAlex Kuznetsov has
Page 11 and 12:
IntroductionResilient T-SQL code is
Page 13 and 14:
IntroductionCh. 02: Code Vulnerabil
Page 15 and 16:
IntroductionSpecific examples demon
Page 17:
IntroductionWhat this book does not
Page 21 and 22:
Chapter 1: Basic Defensive Database
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 57 and 58:
Chapter 2: Code Vulnerabilitiesdue
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74: Chapter 2: Code Vulnerabilities due
Page 75: Chapter 2: Code Vulnerabilities due
Page 78 and 79: Chapter 3: Surviving Changes to Dat
Page 104 and 105: 104
Page 106: Chapter 4: When Upgrading Breaks Co
Page 109 and 110: Chapter 4: When Upgrading Breaks Co
Page 123: Chapter 4: When Upgrading Breaks Co
Page 132 and 133: Chapter 5: Reusing T-SQL CodeThe Da
Page 134 and 135: Chapter 5: Reusing T-SQL CodeIt is
Page 136 and 137: Chapter 5: Reusing T-SQL CodeAverag
Page 138 and 139: Chapter 5: Reusing T-SQL CodeBEGINS
Page 140 and 141: Chapter 5: Reusing T-SQL CodeWe als
Page 142 and 143: Chapter 5: Reusing T-SQL CodeLet's
Page 144 and 145: Chapter 5: Reusing T-SQL CodeStateC
Page 146 and 147: Chapter 5: Reusing T-SQL CodeStateC
Page 148 and 149: Chapter 5: Reusing T-SQL CodeBEGIN
Page 150 and 151: Chapter 5: Reusing T-SQL CodeSELECT
Page 152 and 153: Chapter 5: Reusing T-SQL CodeReusin
Page 154 and 155: Chapter 5: Reusing T-SQL CodeIt is
Page 156 and 157: Chapter 5: Reusing T-SQL CodeINSERT
Page 158 and 159: Chapter 5: Reusing T-SQL CodeListin
Page 160 and 161: Chapter 5: Reusing T-SQL CodeUnique
Page 162 and 163: 162
Page 164 and 165: Chapter 6: Common Problems with Dat
Page 174 and 175:
Chapter 6: Common Problems with Dat
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Chapter 7: Advanced Use ofConstrain
Page 211 and 212:
Chapter 7: Advanced Use of Constrai
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Chapter 8: Defensive ErrorHandlingT
Page 257 and 258:
Chapter 8: Defensive Error Handling
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
show all

Defensive Database Programming - Red Gate Software

Create successful ePaper yourself

Delete template?

Save as template?