Is this for development of production? I'd say use a transaction for starters (http://book.cakephp.org/2.0/en/models/transactions.html) whether in dev or prod mode, then either commit on success or rollback on failure or in dev mode. You could then use some debug or log statements at various points to see what data is affected.
Jeremy Burns Class Outfit http://www.classoutfit.com On 24 Apr 2013, at 12:32, godjen99 <[email protected]> wrote: > I would recommend using Unit Tests. It will take some time to set up the data > (fixtures) and write the tests and such, but it will benefit your whole > project too. > > -- > 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. > > -- 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.
