#6041: Model->find "NOT" does not work as expected
---------------------------+------------------------------------------------
    Reporter:  datac0re    |         Owner:           
        Type:  Bug         |        Status:  new      
    Priority:  Medium      |     Milestone:  1.2.x.x  
   Component:  Model       |       Version:  1.2 Final
    Severity:  Normal      |    Resolution:           
    Keywords:  Model NOT   |   Php_version:  PHP 5    
Cake_version:  1.2.0.7962  |  
---------------------------+------------------------------------------------
Comment (by datac0re):

 I disagree - The cookbook does NOT describe the conditions I'm working
 with here (I had been through them before posting the ticket). They simply
 show the NOT with an IN clause. Since submitting the ticket, I've found I
 can achieve what I'm looking for by doing (notice the double-nested
 array):


 {{{
 'conditions' => array(
  'NOT' => array(array(
    'src' => '',
    'lastapp' => 'MeetMe'
  ))
 )

 Generates:

 WHERE NOT ((src = '' and lastapp = 'MeetMe'))
 }}}

 To me this seems entirely counter-intuitive.

-- 
Ticket URL: <https://trac.cakephp.org/ticket/6041#comment:4>
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 tickets-cakephp@googlegroups.com
To unsubscribe from this group, send email to 
tickets-cakephp+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/tickets-cakephp?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to