2010/9/14 Corey Coogan <[email protected]> > For example, constraint violation, >
You never send something that may fail due a constraint violation. There are corner cases but in most of the cases i do the validation logic in the application, not in the database. > network hiccup, > Ok this is an interesting case. In your first mail you said "if the update to the table A fail, i want to save that value on the table B", if you have a network hiccup you will not be able to save an update in the table B. Better than that.. you want to make to separated call to update something, when the unit of work pattern can make this two updates in one roundtrip.... So maybe you are causing the hiccups with so many calls. You better start implementing loggin at a high level. table rename, etc. > OHHHHHHH!!!! So you are running your application and somebody comes to the database and execute a "table rename"... Instead of wiriting this exception handling code, i will strongly recommend you to find this guy and cut off his fingers. We are not saying that you don't have to handle the exceptions, you have to do the logging stuff! -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
