Submit Enhancement request for this, but testing should be done using the testsuite and use the methods I suggested above.
--
/**
* @author Larry E. Masters
* @var string $userName
* @param string $realName
* @returns string aka PhpNut
* @access public
*/
On 6/19/06, AD7six <
[EMAIL PROTECTED]> wrote:
I think it's probably a moot point but,
being able to truncate a table would have some real uses and not just
for testing. As an example: How about the functionality behind a
"delete all logs" button when you are viewing your log model objects?
Or.. (thinking hard).. having a master and (read only) slave db and
updating the slave by truncating and inserting? You could set up
replicas for that I guess.
Truncate is significantly faster then delete if you have a reasonably
sized table - of course you can just write your own truncate function,
but for an almost one-liner (in it's most primitive form) method it
seems a pity to be missing.
My .02c,
Cheers,
AD7six
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake PHP" 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
-~----------~----~----~----~------~----~------~--~---
