Code-based validation matching, instead of English strings

Ideally, there would be an "fFieldValidationException" class that contains the specific details of each exception. So you could do...

try{
   $user->store();
}catch($e fValidationException){

// < general error catching logic >
$errorMessage = "Oops, something went wrong! ";

// get errors
$errors = $e->getErrors();

// get a specific error
if($errors->hasField('email')){
    // get error object
    $emailError = $errors->getField('email');

    // get various properties (as an example)
    $emailError->getValue(); // "foo@example" - the value
    $emailError->getMessage(); // "The value specified must be unique, however it already exists" - the current English message
    $emailError->getCode(); // "ALREADY_EXISTS" - the error code

    // actual logic
    if($emailError->getCode() == "ALREADY_EXISTS"){
        $errorMessage .= 'This email has already been registered - <a href="#">have you forgot your password</a>?'
        // remove field from array
        $errors->removeField('email');
    }
}

// reset exception array, or, alternatively, create a new exception
$e->setErrors($errors);

// other error handling 
$errorMessage .= " These errors were also found: " . $e->getMessage();

// etc etc
fMessaging::create('error', $errorMessage);

}

EDIT: Changed to a more suitable example.

I'd like to able to release more of that functionality towards the ORM automatic validation mechanism. I often find using a manual fValidation object to be overkill; more often than not, I can simply toss the data straight into the ORM functionality, and it will reject the data if the database finds it invalid. There is, however, no easy way to intercept this validation information from ORM - it comes pre-packaged into the English strings, which is what I'm search of an alternative for.

As a start-off point, this is how it usually works:

try{
     $user = new User(); // set up for fORM
     $user->setUsername(fRequest::get('username'));
     $user->setPassword(fRequest::get('password'));
     $user->setEmail(fRequest::get('email')); // skipping generic email validation
     $user->store();
}catch(fValidationException $e){
     fMessaging::create('error', 'path/to/page', $e->getMessage());
     fURL::redirect('path/to/page');
}

That's how it is now, and I think it should be like the one I posted a couple posts back.

It works remarkably well right now - it lets me rapidly develop applications, because I no longer have to mess around with escaping strings, checking lengths, or checking if that primary key (email) is unique - the ORM system automatically handles that. I wish this custom error list mechanism exists because the data is already there - just not in the format I need it to be in. There's no need for the system to do more work, as the validation is complete. There also needs to be a minimal amount of extra code because, again, the validation has already been done - I just need to catch the error and react accordingly.