Makes sense. Committed in r1157. Trivial change. Thanks to the original poster for reminding us :)
-Dormando Brad Fitzpatrick wrote: > In any case, do it in Store/MySQL.pm, not Store.pm <http://store.pm/> > base class. > > On Tue, Mar 11, 2008 at 12:01 PM, dormando <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > On Mon, 10 Mar 2008, Ask Bjørn Hansen wrote: > > > > > On Mar 10, 2008, at 15:43, Mark Smith wrote: > > > >> AFAIK this trick doesn't work on InnoDB, since they use a flat > >> tablespace TRUNCATE just maps to DELETE FROM anyway. > > > > It does if you use the (recommended) innodb_file_per_table > configuration... > > > > > > - ask > > While you won't reclaim disk space, TRUNCATE TABLE is always fast under > innodb. > > Honestly I thought I fixed this a while ago? Maybe I've been manually > running TRUNCATE TABLE in prod :( > > -Dormando > >
