Restrict Digital Downloads [Support Thread]

[lat9]

Is there cause for concern that the following is generated when using phpMyAdmin "REPAIR" tables?
It sounds like the world is coming to an end. There is one other table with the same error.

The ip2country table uses the default storage engine (ISAM), so I'm not sure why it can't be repaired. Is it perhaps because it's got so many entries?

[RixStix]

The ip2country table uses the default storage engine (ISAM), so I'm not sure why it can't be repaired. Is it perhaps because it's got so many entries?

I was just curious. Don't normally futz with the database but was there trying to figure a different problem when I REPAIR'd the DB and saw those 2 notes.

The entire ZC database is MyISAM utf8_general_ci except:

ip2country
InnoDB
latin1_swedish_ci

AND

flexible_footer_menu
InnoDB
utf8_general_ci

and there are a couple of tables with more rows than the IP2countries table.
Just curious and haven't clue why 2 tables would be InnoDB instead of MyISAM. Much over my paygrade.

[lat9]

I was just curious. Don't normally futz with the database but was there trying to figure a different problem when I REPAIR'd the DB and saw those 2 notes.

The entire ZC database is MyISAM utf8_general_ci except:

ip2country
InnoDB
latin1_swedish_ci

AND

flexible_footer_menu
InnoDB
utf8_general_ci

and there are a couple of tables with more rows than the IP2countries table.
Just curious and haven't clue why 2 tables would be InnoDB instead of MyISAM. Much over my paygrade.

** OFF-TOPIC ALERT **

That's weird. A lot of the database interfaces are "above my pay grade", but I have seen the utf8/latin1 collation mixture on databases that started out as latin1, were converted to utf8 using the convert_db2utf8 tool and then added one or more tables.

The issue there (which I've subsequently corrected with an updated version of that plugin) is that the overall database's default collation was still a form of latin1 so that the newly-added tables wound up with that collation type.

I'd suggest downloading the updated version of that plugin (v4) and running that against your database to (a) set the overall collation to utf8 and (b) set the collation for the ip2country table also to utf8.

I have no clue why the storage-engine for the ip2country table wound up being InnoDB (unless there's also a storage-engine default) ... but any discussion along those lines should be started as a separate thread.