Issue Bug Closed

#84137DB compare must show DB errors if compare fails

Georg Ringer 03/05/18, 08:37 updated 10/02/18, 10:50

Description

If compare fails because of wrong SQL, it must also show the error and not just a warning that it failed – that is really not helpful …

example part for ext_tables.sql

CREATE TABLE tx_fo (
    uid int(11) NOT NULL auto_increment,
    pid int(11) DEFAULT '0' NOT NULL,
    tstamp int(11) DEFAULT '0' NOT NULL,
    table_name varchar(255) NOT NULL DEFAULT '',
    record_id  int(11) DEFAULT '0' NOT NULL,,
    status tinyint(4) DEFAULT '0' NOT NULL,
    user int(11) DEFAULT '0' NOT NULL,

    PRIMARY KEY (uid),
    KEY parent (pid)
);

problem is the double comma at the end of line 6.

Reviews 1