NO BUG: SQL errors with new filters tables

Running MariaDB 5.5.68

I was getting an error from the wp cron that the “bricks_filters_index_job” table doesn’t exist so doing some checks in your code in “query-filters.php” I see a new table should have been created at some point since v1.10. So using the info from your script I tried to create the table manually with the following SQL

CREATE TABLE l5l9U_bricks_filters_index_job (
job_id BIGINT(20) NOT NULL AUTO_INCREMENT,
filter_row_id BIGINT(20) UNSIGNED,
job_details LONGTEXT,
total BIGINT(20) UNSIGNED default ‘0’,
processed BIGINT(20) UNSIGNED default ‘0’,
job_created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
job_updated_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
PRIMARY KEY (job_id),
KEY filter_row_id_idx (filter_row_id)
);

But I get the error “there can be only one TIMESTAMP column with CURRENT_TIMESTAMP”

So I guess when bricks went to create the table originally it also got this error but never reported it which is why no table exists.

I am thinking it may be a MariaDB version compatibility issue?

Hi @SpinDreams ,

Yes, MariaDB 5.5 is outdated.
The SQL to create the table is not supported for 5.5

WordPress recommended requirements

Kindly update the environment.

Regards,
Jenn

I updated MariaDB and the index was created so now I am cooking on gas. Thanks.

1 Like