#5781: Model::set Bug / Issue
-----------------------------------------------------+----------------------
Reporter: redcomet | Owner:
Type: Bug | Status: reopened
Priority: Low | Milestone: 1.2.x.x
Component: Model | Version: RC3
Severity: Minor | Resolution:
Keywords: set,keys,schema,model,beforevalidate | Php_version: PHP 5
Cake_version: |
-----------------------------------------------------+----------------------
Changes (by redcomet):
* status: closed => reopened
* resolution: wontfix =>
Comment:
That can't be true, even if the set function is meant to output that
'wrong' data when the data keys do not match the schema, it should at
least check ALL of the keys, not just the first one.
For instance, if I moved the city input to the top of the form and
submitted (without my change to the set function) it works perfectly.
When the address1 field is on the top it fails and returns the 'bad' data
and does not set $this->data at all.
Any time that a function does two different things when presented with the
same data seems like it would be a at least a minor bug.
--
Ticket URL: <https://trac.cakephp.org/ticket/5781#comment:2>
CakePHP : The Rapid Development Framework for PHP <https://trac.cakephp.org/>
Cake is a rapid development framework for PHP which uses commonly known design
patterns like ActiveRecord, Association Data Mapping, Front Controller and MVC.
Our primary goal is to provide a structured framework that enables PHP users at
all levels to rapidly develop robust web applications, without any loss to
flexibility.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"tickets cakephp" 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/tickets-cakephp?hl=en
-~----------~----~----~----~------~----~------~--~---
