[Koha] Sessions table corrupt in Koha 3.0

[Mason James]

On 2012-01-14, at 6:14 PM, ed c wrote:

> Truncating should work fine, but I saw somewhere (I think in the e-mail archives not positive), that it could take longer. I'm not sure that is true or not since I didn't try it. The advantage to truncate though would be I wouldn't have had to look up how to recreate the table.
> 
> Edward
> From: Mason James <mtj at kohaaloha.com>
> To: Jared Camins-Esakov <jcamins at cpbibliography.com> 
> Cc: ed c <terrapin44 at yahoo.com>; "koha at lists.katipo.co.nz" <koha at lists.katipo.co.nz> 
> Sent: Friday, January 13, 2012 10:22 PM
> Subject: Re: [Koha] Sessions table corrupt in Koha 3.0
> 
> 
> On 2012-01-14, at 6:01 AM, Jared Camins-Esakov wrote:
> 
> > Edward,
> > 
> > Drop the table then recreate it. Your users will have to log in again, but that's it. I'm not sure that will reclaim the disk space, though.
> > 
> 
> 
> just curious, why not just truncate the table?

aaah, that Q was for Jared... :) 

but answering my own question, i guess its because for the default inno-db config for mysql, a truncate wont delete the existing space for that table - where as a drop/create will
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 535 bytes
Desc: This is a digitally signed message part
URL: <http://lists.katipo.co.nz/pipermail/koha/attachments/20120114/9b6bad3a/attachment-0001.pgp>