Re: [bv-dev] Feature Suggestion :: Implicit constraints
On 29 Jul 2014, at 18:01, Richard Fanning <Richard.Fanning(a)FINEOS.com> wrote:
Another scenario in our company where we thought this feature might be useful was again
around the area of defaults. So for example a String property on an @Entity would not need
to define any @Size but a sensible default (255) would apply akin to JPA providers [1]
But we’d still like to get ConstraintViolations during validation phase rather than some
JPA/DB errors complaining about the strings length.
Actually, I’ve been trying to convince the JPA EG to do the opposite. The @Column(lengh)
would be guessed by @Size(max=200) to avoid repetition. But I have had some resistance on
this approach.
Attachments:
- attachment.html (text/html — 2.0 KB)