On 30.05.2011 12:50, Tim Nagel wrote: > I believe using an ORM annotation to specify how a property should be > mapped into a database column is separate from defining a php datatype > of a property. @var != @ORM\Column > > > t > > On Mon, May 30, 2011 at 19:13, Christian Heinrich > <[email protected]> wrote: >> What if I don't want an attribute to be mapped, but want the @var >> annotation to help my editor with code completion?
There are two different aspects, if you don't want it mapped, don't put @ORM\Column, all good. But if you want it mapped, you should not have to specify the data type in both @var AND @ORM\Column, that's all I'm saying. Note that the type thing is one example, but I suspect this could apply to other things that maybe don't exist in phpdoc but that could be new standard annotations. Cheers -- Jordi Boggiano @seldaek - http://nelm.io/jordi -- 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
