StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13318293
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-11-10T01:19:24.703
FavoriteCount
0
LastActivityDate
2012-11-10T01:25:24.117
LastEditDate
2012-11-10T01:25:24.117
LastEditorUserId
1312094
OwnerUserId
1312094
ParentId
11632100
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Annotations are great, and we're using them with code generation so that we can define form element behaviors based on the schema properties returned by the Doctrine EntityManger. I was hopeful that annotations would put more of the entity definition in one place and make them easier to manage, and so far this has been true. That being said, I've found annotations a bit inflexible, in that the attributes assigned by annotation, cannot be overridden with other annotations in a sub-class. It is easy to override attributes set with annotations at runtime, but you can't do it with more annotations. (May be stating the obvious.) So I'm doing overrides in my controller actions at the moment. Example: <pre><code> $builder = new AnnotationBuilder(); $form = $builder->createForm($myEntity); // customize the the InputFilter for myElement $form->getInputFilter()->get('myElement')->setAllowEmpty(FALSE); $form->getInputFilter()->get('myElement')->setRequired(TRUE); $form->getInputFilter()->get('myElement')->getValidatorChain()->addValidator(new \Zend\Validator\NotEmpty('all')); // carry on with the form as normal $form->setData($this->getRequest()->getQuery()); </code></pre> As I've only just started needing to apply custom validation rules, and expect these to get more complicated over time, and perhaps even conditional, I expect I'll want to move my form builder out of the Controllers and into the Models. The reason being, when/if I start defining validation rules that are conditional, that logic is in the Model where it belongs. This will clean up the Controller actions too, as all the form assembly gets turned into a black box method. Example: <pre><code> $form = $myEntityModel->buildForm($myEntity); // carry on with the form as normal $form->setData($this->getRequest()->getQuery()); </code></pre> So I don't think it matters whether or not you use annotations to define your default input rules. You are going to modify those according to business logic regardless of how you initially define them. It sounds to me like you might benefit from moving form assembly into your model classes to achieve your goal of keeping validation rules entirely separated from the entity. I believe your instinct is correct that business logic needs to stay in the models, not in the controllers or entities.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POZF2 Rest Service/Doctrine Validation
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USdualmon
UserOwnerUserId
1. USdualmon
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

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.