Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I'm wondering why module doesn't support a backup of the table properties such as engine, charset and comment:
ENGINE=InnoDB DEFAULT CHARSET=utf8 and so on.
This is actually required piece of the schema as soon as dump is being restored. It would be greatly appreciated to have such feature in place.
Comments
Comment #1
bigjim CreditAttribution: bigjim commented+1
Comment #2
dboulet CreditAttribution: dboulet commented+1. Without this all my restored tables get created as MyISAM.
Comment #3
Shai CreditAttribution: Shai commented+1
Comment #4
ronan CreditAttribution: ronan commentedI'm using a 'show create table' sql command to generate the table create so I'm not sure why it wouldn't be returning the full table schema in your case. Can you run 'show create table node' on your server using the mysql command line (or phpMyAdmin) and let me know what the output is? What version of MySQL are you using?
Thanks
Comment #5
ronan CreditAttribution: ronan commentedI looked into this further and it looks like DBTNG sets the db to ANSI, TRADITIONAL mode which doesn't expose the extra table info. I'll need to switch this mode back during export. I'll have to do some testing to figure out if this breaks anything else.
Comment #6
ronan CreditAttribution: ronan commentedThe latest dev should fix this by setting the SQL_MODE before creating the dump. Let me know if it's working.
Comment #7
dboulet CreditAttribution: dboulet commentedDoesn't seem to have made any difference for me. Is there anything special that should be done to get it to work?
Comment #8
dboulet CreditAttribution: dboulet commentedLooks like I spoke too soon, seems to be working today.