Cannot Save anything, error about duplicate entries

have you inspected your database tables for any issues that need repair?

Moving to support request as I can't recreate this issue on any of my sites.

Apparently it is trying to do an insert when the data already exists with the exact same values:

mysql> describe drupal1_views_view;
+--------------+------------------+------+-----+---------+----------------+
| Field | Type | Null | Key | Default | Extra |
+--------------+------------------+------+-----+---------+----------------+
| vid | int(10) unsigned | NO | PRI | NULL | auto_increment |
| name | varchar(32) | NO | UNI | | |
| description | varchar(255) | YES | | | |
| tag | varchar(255) | YES | | | |
| view_php | blob | YES | | NULL | |
| base_table | varchar(64) | NO | | | |
| is_cacheable | tinyint(4) | YES | | 0 | |
+--------------+------------------+------+-----+---------+----------------+
7 rows in set (0.03 sec)

mysql> select * from drupal1_views_view where name = 'most_downloaded';
+-----+-----------------+---------------------------+---------+----------+------------+--------------+
| vid | name | description | tag | view_php | base_table | is_cacheable |
+-----+-----------------+---------------------------+---------+----------+------------+--------------+
| 32 | most_downloaded | The most downloaded files | default | | node | 0 |
+-----+-----------------+---------------------------+---------+----------+------------+--------------+
1 row in set (0.02 sec)

mysql>

Any clues?

Hm. As a quick fix you can probably export your view (to ensure you still have a copy) and manually delete it from the database. Be sure to get the 'vid' of the view and delete all of the views_display records associated with it as well.

When I went to delete the view I was working on, it deleted it, but also took me to another Page not Found error. I'm beginning to think this is something bigger than Views, but is only showing up so far when I do certain admin things. I'm going to have to keep looking into this to find what the problem is.

The error appears to have been the result of some bad caching I think. It has disappeared as mysteriously as it appeared.

Automatically closed -- issue fixed for 2 weeks with no activity.