Doctrine 2 doesn't do validation inside the ORM, although it apparently supports hooks for it, if I've followed Jon Wage's recent commentary correctly. So in Symfony 2.0 it's likely that most validation would be in forms.
Also, there are lots of model layer possibilities out there other than Doctrine (or even SQL-based ORMs in general), and how does one present those errors back to the user easily or offer client-side validation if they are only known to the model? On Mon, Mar 15, 2010 at 2:05 PM, Jacob Coby <[email protected]> wrote: > > On Mar 14, 2010, at 4:16 PM, Bernhard Schussek wrote: > >> The validation in Symfony 2 is handled by a seperate Validator >> component. Its meta data, i.e. validated classes, properties and also >> error messages can all easily be accessed. Parsing the meta data for >> error messages and writing the non-translated ones to a file should >> not be a problem. > > Why not make the models responsible for data validation? I've never > understood the desire to require the use of form objects. > > -- > Jacob Coby > > > > > > > -- > If you want to report a vulnerability issue on symfony, please send it to > security at symfony-project.com > > You received this message because you are subscribed to the Google > Groups "symfony developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > -- Tom Boutell P'unk Avenue 215 755 1330 punkave.com window.punkave.com -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
