Just deleting an outdated comment.
Cleaning existing test in ERR_Handler_TEST and adding another test. The latter is basically the same as the one named testErrorRecordCreation in REL_Relationships_TEST, but using a simple insert instead of database.insert.
With this design we roll everything back if any error happens in a trigger. We avoid leaving the database in an inconsistent estate, avoid issues with reentrant flags, and still store errors in the database.
Adding apex:pageMessages element to pages that did not have it. This way the user will receive user-friendly feedback.
Undoing a saveError that I had done before. No point in trying to save those errors. If the field is not updatable we will just ignore it.
Example of how to wrap an action method in a try-catch and save errors after rollback.
Turns out we don't need to add the error messages to the records. If there are exceptions the system will do it for us.
Fixing test (seems like it should not have been working with my latest fix - even though it did).
Fixing tests (they need more work).
Merge dev into feature/190-proper-dml
Trigger refactoring.
Merge branch 'feature/190-proper-dml' of https://github.com/SalesforceFoundation/Cumulus into feature/190-proper-dml
Deleting commented-out code.
Forgot that I had moved the try-catch and savepoint/rollback to the TriggerHandler last Friday.
Adding test. Does not behave as we would like (error record does not get saved), but that's how the platform works if you use the Database DML methods...
Checking the size of Trigger.new in a debug statement was causing tests to fail.
Merge pull request #217 from SalesforceFoundation/feature/190-proper-dml

Feature/190 proper dml