Skip to content
  • Sivert Sorumgard's avatar
    16ce5272
    Bug#27960500: UPGRADE 5.7 -> 8.0.11 -> 8.0.{12,13} FAILS DUE TO FTS TABLES WITH 0 TIMESTAMPS · 16ce5272
    Sivert Sorumgard authored
    The hidden FTS "tables" were created by InnoDB with 0 timestamps
    for 'created' and 'last_altered' on upgrade from 5.7, and for new
    tables created in 8.0.11.
    
    Upon a DD upgrade from 8.0.11 to 8.0.12, new DD tables are created,
    and meta data is migrated to the new tables by INSERT statements.
    This failed because 0 timestamps are not accepted with the server
    default SQL mode.
    
    This patch does the following:
    
    1. Make sure FTS tables are created with correct timestamps.
    2. Add an upgrade step when upgrading from before 8.0.12 to
       correct the 0 timestamps to CURRENT_TIMESTAMP before the
       meta data is migrated.
    
    Additionally, error reporting from server side SQL statement
    execution is improved.
    
    Change-Id: Ic373931c3dd2ba46314c0d0c689ff0e8db61fa8e
    16ce5272
    Bug#27960500: UPGRADE 5.7 -> 8.0.11 -> 8.0.{12,13} FAILS DUE TO FTS TABLES WITH 0 TIMESTAMPS
    Sivert Sorumgard authored
    The hidden FTS "tables" were created by InnoDB with 0 timestamps
    for 'created' and 'last_altered' on upgrade from 5.7, and for new
    tables created in 8.0.11.
    
    Upon a DD upgrade from 8.0.11 to 8.0.12, new DD tables are created,
    and meta data is migrated to the new tables by INSERT statements.
    This failed because 0 timestamps are not accepted with the server
    default SQL mode.
    
    This patch does the following:
    
    1. Make sure FTS tables are created with correct timestamps.
    2. Add an upgrade step when upgrading from before 8.0.12 to
       correct the 0 timestamps to CURRENT_TIMESTAMP before the
       meta data is migrated.
    
    Additionally, error reporting from server side SQL statement
    execution is improved.
    
    Change-Id: Ic373931c3dd2ba46314c0d0c689ff0e8db61fa8e
Loading