[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Koha-bugs] [Bug 1016] New: Crashed mySql tables
From: |
bugzilla-daemon |
Subject: |
[Koha-bugs] [Bug 1016] New: Crashed mySql tables |
Date: |
29 Aug 2005 15:47:15 -0000 |
http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1016
Summary: Crashed mySql tables
Product: Koha
Version: 2.2.0
Platform: PC
OS/Version: Windows 2000
Status: NEW
Severity: enhancement
Priority: P2
Component: Database
AssignedTo: address@hidden
ReportedBy: address@hidden
QAContact: address@hidden
This is some enhancement you may think about.
The other day marc_subfield_table crushed. (How? Don't ask.) Nobody realised
and Koha did not complain at all. We went on adding and modifying about 200
biblios without realising anything. Unless you go to see the MarcDetails
everything looks fine. We found out on a un-routine Mysql tables check this
was the case. What happened was that all the tables were being filled properly
but the marc_subfield_table.
The cleaning of the database was a little bit messy. It took more than half a
day plus reentering all the data.
We panicked so much that we added two lines to addbiblio.pl and additem.pl
which locks and unlocks all the necessary times momentarily and on error
returns you to mainpage.pl with error message "Contact automation for Mysql
error". This way no addition or modification of tables is possible untill
problem resolved.
I know that this is not a common problem and yes I do not know how we managed
to crush the table but yes tables do crash so it may be something to consider
committing such a control in your script. Even if not committing I'll
appreciate any better (faster) way of checking Mysql-health at least for us to
use.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Koha-bugs] [Bug 1016] New: Crashed mySql tables,
bugzilla-daemon <=