Jump to content

Thomas_B

Clients
  • Posts

    19
  • Joined

  • Last visited

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Everything posted by Thomas_B

  1. *SOLVED* Yesterday my host upgraded to mySQL 5.7, which included changing to the Barracuda file format (previously Antelope). So now the SQL commands were successfully executed and my "compact" database tables have been converted to "dynamic." So I'd like to report a happy ending to my adventure. A big Thank You to the forum members for the advice and providing the SQL commands to do it. - Thomas
  2. mySQL 5.6. It's a hosted server. Tech support says that mySQL will be upgraded to 5.7 in a few weeks. But they cautioned that what I want to do is probably not going to work; The account is on a shared server and changing to the Barracuda file format would probably require a global setting that would affect all shared users. But others have commented that they were told a similar story by their host. And yet they were still able to change to DYNAMIC row format. So I need advice on how to make this magic happen. - Thomas
  3. I'm not having any joy applying the DYNAMIC row conversion on my seven COMPACT tables. For example, when I execute this: ALTER TABLE ibf_core_follow_count_cache ROW_FORMAT=DYNAMIC; It reports my InnoDB file format is wrong. I get two warnings (and the row format remains in the compact mode): Warning: #1478 InnoDB: ROW_FORMAT=DYNAMIC requires innodb_file_format > Antelope. Warning: #1478 InnoDB: assuming ROW_FORMAT=COMPACT. So then I added these two statements to the my.cnf file on my paid hosting site: innodb_file_format=BARRACUDA innodb_large_prefix=1 Repeated the ALTER TABLE statement and still no joy. So I'm seeking advice on how to do the COMPACT to DYNAMIC row conversion on my tables. - Thomas
×
×
  • Create New...