[Koha] Sessions table corrupt in Koha 3.0
Jared Camins-Esakov
jcamins at cpbibliography.com
Sun Jan 15 01:58:51 NZDT 2012
Mason,
On Sat, Jan 14, 2012 at 3:57 AM, Mason James <mtj at kohaaloha.com> 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.
> >> 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
That was my reasoning. It's possible that was unnecessary, but given that
the problems all started when the system ran out of disk space, it seemed
like a worthwhile precaution.
Regards,
Jared
--
Jared Camins-Esakov
Bibliographer, C & P Bibliography Services, LLC
(phone) +1 (917) 727-3445
(e-mail) jcamins at cpbibliography.com
(web) http://www.cpbibliography.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.katipo.co.nz/pipermail/koha/attachments/20120114/f58b113e/attachment.html>
More information about the Koha
mailing list