Yeah, I'm finding that one out the hard way.
Still, even using find(first), the new field does not yet read into the
database, until I specify it in the fields list.
I guess I have a work around, but it's something I'll be eyeing with a bit
of suspicion. Doesn't help that I updated to CakePHP 2.3.6, and the update
to the license string means just about every lib/Cake program received an
alteration.
On Tuesday, June 11, 2013 7:15:59 PM UTC+10, euromark wrote:
>
> dont use read(), use find(first)
> read() does too many thinks people are not aware of and possibly messing
> things up in the long run
>
>
> Am Dienstag, 11. Juni 2013 05:52:04 UTC+2 schrieb Reuben:
>>
>> Hi
>>
>> I've put a new field on a table, and it's not being read as a part of a
>> read(null, $id) operation.
>>
>> I have made sure I have delete the cache, and I can definitely see that
>> the new field is there.
>>
>> Additionally, if I do a read(array('id', 'notify_email'), $id), the new
>> field (which is notify_email), is present, just not when I do a read(null,
>> $id).
>>
>> Regards
>> Reuben Helms
>>
>
--
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP
---
You received this message because you are subscribed to the Google Groups
"CakePHP" 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/cake-php?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
