Check if any error occurs on database level. In debug output, see if there is a 'rollback'. If so, make sure all queries that should be executed on saveAll are there. If they are, try to execute the transaction directly on database and make sure that it works fine. I had an experience with an error on database level which has not invalidated the saveAll.
On Friday, April 23, 2010, cricket <[email protected]> wrote: > On Apr 22, 6:42 pm, Lucca Mordente <[email protected]> wrote: >> To use 'validate'=>false as you are, disables the validation! > > Sorry, I should have mentioned that disabling validation was just > something I was trying to see if that was the problem. The data is not > saved either way. > >> So, this way, saveAll will always return 1 > > That doesn't make any sense to me. I don't think the method should > return true if the save does not occur, regardless of whether > validation is disabled or not. > > I'm using 1.2.6, btw. Bad me for not specifying that. > > Check out the new CakePHP Questions site http://cakeqs.org and help others > with their CakePHP related questions. > > You received this message because you are subscribed to the Google Groups > "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/cake-php?hl=en > -- Lucca Mordente Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "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/cake-php?hl=en
