• I can “check” my SQL database using a couple of different methods:
    – I can sign into my web hosting account, go to the cPanel, click “MySQL Databases,” then use the “Check Database” function.
    – I can use the “BackWPup” plugin to back up my WordPress site, which checks the SQL database as part of its process.

    Either way, the first time I checked my SQL database after using this plugin for a while I got the following warning:

    “wp_wct_list: Found row where the auto_increment column has the value 0”

    When I Deactivated and Deleted the plugin and rechecked my SQL database, that warning disappeared.

    When I reinstalled the plugin and then immediately checked my SQL database again, that warning returned.

    Using the “phpMyAdmin” function in my hosting cPanel, I looked at the “wp_wct_list” SQL table in my database. It’s one of 7 SQL tables that the plugin initially installs, and it contains a list of the data Tables managed by this plugin. Initially it contains two predefined rows (entries):
    – id=0, name=”Archive”, corresponding to the “Article Archive” data Table
    – id=1, name=”Demo DB”, corresponding to the “Demo DB” data Table containing 210 sample items
    And as I create my own data Tables, more rows appear in this SQL table.

    Apparently, an SQL table can declare one of its columns (fields) to be the “auto_increment column,” and in general such a column is not supposed to have a 0 value in any row of that table.

    However, this “wp_wct_list” SQL table violates that guideline by both declaring “id” to be the “auto-increment” column and by having a row with id=0, which triggers that warning. None of the plugin’s other SQL tables have a row with id=0.

    So, my question is this: Does your “wp_wct_list” SQL table really need “id” to be the “auto_increment” column? Or can its “A_I” attribute be turned off, presumably eliminating this warning?

    Thanks!

    Martin

  • The topic ‘This plugin causes an “auto_increment” warning when checking the SQL database’ is closed to new replies.