Your code and schema are OK. You probably trying on previous version of table. http://sqlfiddle.com/#!2/9dc64/1/0 Your table even has no UNIQUE, so that error is impossible on that table. Backup data from that table, drop it and re-create. Maybe you tried to run that CREATE TABLE IF NOT EXIST. It was not created, you have … Read more
The main reason why the error has been generated is because there is already an existing value of 1 for the column ID in which you define it as PRIMARY KEY (values are unique) in the table you are inserting. Why not set the column ID as AUTO_INCREMENT? CREATE TABLE IF NOT EXISTS `PROGETTO`.`UFFICIO-INFORMAZIONI` ( … Read more
If you can make the dump again you could add –insert-ignore to the command-line when dumping. Or you can try using the mysqlimport command with –force,which will continue even if it encounters MySQL Errors.
This will happen if the table contains an existing record with an id of 0 (or negative). Updating all existing records to use positive values will allow auto_increment to be set on that column. Edit: Some people asked how that 0 got in there. For clarification, the MySQL Reference Manual states that “For numeric types, … Read more
manage.py dumpdata –natural will use a more durable representation of foreign keys. In django they are called “natural keys”. For example: Permission.codename is used in favour of Permission.id User.username is used in favour of User.id Read more: natural keys section in “serializing django objects” Some other useful arguments for dumpdata: –indent=4 make it human readable. … Read more