On Thu, Oct 12, 2006 at 04:52:23PM -0500, Carlos Mario Medina Marín wrote:
> Query Failed - table_insert(severity) - insert into severity
> (severity,bgcolor,fgcolor) VALUES
> ('New Severity','000000','FFFFFF') - Duplicate entry '127' for key 1
>
> I have changed the 127 level in the severity form, but when I click on save
> button it doesn't take the new value and show a problem with the 127 entry.
key 1 is usually the primary key and that is usually for id.
This is not "why mysql sucks" list but suffice to say, mysql is a bit
confused. It thinks the next available id is 127, but at the same time
it knows 127 is used; great isn't it?
start a mysql client and type:
REPAIR TABLE severity;
That should do it.
- Craig
--
Craig Small GnuPG:1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5
Eye-Net Consulting http://www.enc.com.au/ MIEE Debian developer
csmall at : enc.com.au ieee.org debian.org
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
jffnms-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jffnms-users
