StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6484960
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2011-06-26T15:46:36.177
FavoriteCount
0
LastActivityDate
2011-06-26T15:46:36.177
LastEditDate
LastEditorUserId
0
OwnerUserId
146124
ParentId
6288794
PostTypeId
2
Score
7
ViewCount
0
LastEditorDisplayName
text
Body
As i was reading through your post, a question came into my mind about what you write: Why, instead of validating a form, dont you validte your model's objects? I mean, in an OOP way of looking things your model´s object (or domain objects) are the ones who knows what data is valid or not for each of their attributes. Not doint that, and pushing that logic into the UI makes your design fragile, UI dependant and harder to maintain. If you add a new attribute to one of your model's object, you'll have to modify the form validator as well. If you go with Objects Validation, the idea is that an object cannot be created in an invalid state. If you try to modify it with invalid data, an exception will be thrown. This makes easy to work with forms. The only think you have to do is populate your objects and watch for exceptions thrown in that process. This is only an idea to get you started and see another way of solving this problem. Regarding your question about Forms Validation, as the other guys said, it is always better not to reinvent the wheel and go for an existing, proven, validation framework. However, if you are curious about it, here is one of the many ways you can do it: Let's go through the things you need: you are talking about a form that needs to be validated with one or more validation functions. Then you talk about a function that tells you whether the form passed the validation or not, and as a result you got the list of errors found during the validation phase. As you talk about OOP, the way to go is to give each concept or idea of your problem domain (the domain of form validation) entity via a class that represents it that model the behavior they have. So, it is natural to think about a <code>FormValidator</code> class with a list of <code>ValidationRule</code> instances, where each one colaborates in the validation process. This validation process is done by calling the <code>validate</code> function of the <code>FormValidator</code>. Also, each <code>ValidationRule</code> will give, as result of calling it´s own <code>validate</code> method an instance of the <code>ValidationRuleResult</code> class, that tells whether the validation was successful or not, along with an error message and additional data (if needed) about the validation. Once all the validation rules were evaluated, the <code>validate</code> method of the <code>FormValidator</code> class will return an instance of <code>ValidationResult</code> class, that summarizes all the validation results of the rules evaluated providing the list of errors found. To get this down to earth, here is the sample model we're talking about: A sample implementation Disclaimer: please bear in mind that, as any design, it may contains flaws. The following is intended to help you to solve your problem, not to be a complete solution. <pre><code>class FormValidator { private $_validationRules; function __construct() { $this->_validationRules = array(); } // Registers a new validation rule function addRule($aValidationRule) { $this->validationRules[] = $aValidationRule; } // Validates $aForm, evaluating each of the $_validationRules defined function validate($aForm) { $aValidationResult = new ValidationResult(); foreach($this->_validationRules as $aValidationRule) { $aValidationRuleResult = $aValidationRule->validate($aForm); $aValidationResult->addResult($aValidationRuleResult); } return $aValidationResult; } } abstract class ValidationRule { private $_fieldName; // The form's field name to be validated function __construct($aFieldName) { $this->_fieldName = $aFieldName; } function fieldName() { return $this->_fieldName; } // Returns an instance of ValidationResult describing the result of evaluating the ValidationRule in $aForm. abstract public function validate($aForm); } class ValidationResult { private $_validationRuleResults; function __construct() { $this->_validationRuleResults = array(); } // Registers a validation rule result function addResult($aValidationRuleResult) { $this->_validationRuleResults[] = $aValidationRuleResult; } // Returns the list of the error messages of the validation rule results that did't passed function errorsFound() { $errors = array(); foreach($this->validationRuleResults as $aValidationResult) { if ($aValidationResult->passed()) continue; $errors[] = $aValidationResult->errorMessage(); } return $errors; } // Tells whether all the validation rule results passed or not function validationPassed() { foreach($this->validationRuleResults as $validationResult) { if ($validationResult->passed() == false) return false; } return true; } } class ValidationRuleResult { private $_passed, $_error_message; function __construct($passed) { $this->_passed = $passed; $this->_error_message = ''; } // Tells whether the form passed this validation rule or not public function passed() { return $this->_passed; } public function // The error message should be empty if passed to avoid confusion public function errorMessage { return $this->passed() ? '' : $this->_error_message; } public function setErrorMessage($anErrorMessage) { $this->_error_message = $anErrorMessage; } } </code></pre> You can create a validation rule this way: <pre><code>class NotEmptyValidationRule extends ValidationRule { public function validate($aForm) { $fieldName = $this->fieldName(); $fieldValue = $aForm[$fieldName]; $passed = !empty($fieldValue); $result = new ValidationRuleResult($passed); if (!$passed) { $result->setErrorMessage("$fieldName cannot be empty"); } return $result; } } </code></pre> Some things to note: <ul> <li>Im assuming that $aForm is an associative array of field name / value</li> <li>You can note that if a validation rule passes, the result is not used (as the <code>ValidationResult</code> class works only on those results that didn't pass). Remember that this is a sample only for the purpose of helping you, is not a complete solution.</li> </ul> Usage <pre><code> $rule = new NotEmptyValidationRule('name'); $validator = new FormValidator(); $validator->addRule($rule); $aForm = $__POST['myForm']; $validationResult = $validator->validate($aForm); if ($validationResult->validationPassed()) { $errorsFound = $validationResult->errorsFound(); // do something with the $errorMessage $errorMessage = array_join(' ', $errorsFound); } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POStructure of a form validation class
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USnick2083
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POStructure of a form validation class
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COHey- just came back to this question and saw this very detailed answer. Thanks for taking the time- very helpful.
 singulars
 PostPostId
 PO
 UserUserId
 USJanee
2. CO@Janee, your're welcome :) I'm glad it was helpful to you. Cheers!
 singulars
 PostPostId
 PO
 UserUserId
 USnick2083

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.