Timeline for Ignoring Validation rules when deploying code
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 8, 2012 at 2:51 | comment | added | Ralph Callaway | Lol, just answered this and you'd already put in my two cents for me. Hope you're doing well caleb | |
| Aug 2, 2012 at 11:55 | comment | added | Born2BeMild | I prefer the use of a specify no-validation profile rather than turning validation off for all users. | |
| Aug 1, 2012 at 15:44 | comment | added | David Gillen | I am in agreement that the first option, to update all legacy code, is the ideal scenario. Unfortunately I've come across real world instances where there were 10,000s of lines of legacy code and associated unit tests which were failing due to new validation rules. This code was written by a third party who was no longer present. The cost of updating all this unknown code what more than prohibitive. | |
| Aug 1, 2012 at 14:48 | history | answered | caleb | CC BY-SA 3.0 |