Perhaps i'm not being clear. Some yaml...
edit:
display:
"item details": [ stocknumber, description, price ]
My form also has several fields that are not displayed. For instance
'updated_at'. I would expect that the symfony automagic update_at
field would still work properly with the above generator.yml but it
actually writes a null value to the database. In order to get the
'updated_at' field working properly, I have to unset that field in the
form class. In fact, all fields that are not included in the display
option (excluding id) get written to the database with a null value
unless I unset them in the form class.
To my mind, not including the field in the display option should have
the same effect as unsetting it.
Do you see what I mean now??
On 29 Dec 2008, at 22:51, Damien Lepage wrote:
> Hi,
>
> I think there is a good reason: the form is shared between different
> views and you have different levels of configuration for them. For
> example, it does not make sense to unset a field because it is not
> displayed in the list view. It does not make sense either to unset a
> field because it is not displayed at the form level because the
> display option could be overriden for the edit or new view.
>
> Damien
>
>
>
> 2008/12/29 Jonathan Franks <jonat...@ifranks.com>
>
> Yes, it is the behavior but is it the intended behavior??
>
> I can't think of any reason why the generator.yml display option
> behaves like this. To me, it seems like a bug. But i'm wondering if
> there is a good reason that I've missed?....
>
>
>
>
> >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
-~----------~----~----~----~------~----~------~--~---
