before I go ahead and change lots of integer fields of my db that have _, can someone please confirm if this is actually an issue with integer fields? I need to be sure about this before changing because I have many such fields, a nightmare!
On Tue, Feb 18, 2014 at 10:59 PM, Nima Sadjadi <[email protected]> wrote: > Can someone explain why fields with _ should be a problem if the type is > integer when flushing? but without _ is okay! > I have this when flushing > $this->cGroup = 1; > > here is field definition: > > $metadata->mapField(array( > 'fieldName' => 'cGroup', > 'columnName' => 'c_group', > 'type' => 'integer', > 'nullable' => false, > 'unsigned' => false, > 'comment' => '', > 'default' => '', > )); > > > > On Tue, Feb 18, 2014 at 10:40 PM, Nima Sadjadi <[email protected]> wrote: > >> I had an integera not nullable field as c_group (of course property is >> cGroup) when I wanted to flush/insert a new record, i was get always error >> that it can not be nulled with sqllogget I saw it was null but I actually >> had passed a value to it for insert, but when I renamed the field in db to >> 'group' and applied the changes in entity, problem fixed! This is very >> strange, why integer fields/properties should have problem with _ like >> c_group or may be with caps property as cGroup?! >> I had no such problems with string fields like first_name, but with >> integer fields! >> >> >> > > -- You received this message because you are subscribed to the Google Groups "doctrine-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/doctrine-user. For more options, visit https://groups.google.com/groups/opt_out.
