Invalid default value for 'user_registered' - Wordpress

-

Issue:

When I import the following sql create statement

mysql> CREATE  TABLE IF NOT EXISTS `erp`.`je_menus` (      ->   `id` INT(11) NOT NULL AUTO_INCREMENT ,      ->   `name` VARCHAR(100) NOT NULL ,      ->   `description` VARCHAR(255) NOT NULL ,      ->   `live_start_date` DATETIME NULL DEFAULT NULL ,      ->   `live_end_date` DATETIME NULL DEFAULT NULL ,       ->   `notes` VARCHAR(255) NULL ,      ->   `create_date` TIMESTAMP NOT NULL DEFAULT  '0000-00-00 00:00:00',      ->   `created_by` INT(11) NOT NULL ,      ->   `update_date` TIMESTAMP NOT NULL DEFAULT  CURRENT_TIMESTAMP  ,      ->   `updated_by` INT(11) NOT NULL ,       ->   `status` VARCHAR(45) NOT NULL ,      ->   PRIMARY KEY (`id`) )       -> ENGINE = InnoDB;

giving following error

ERROR 1067 (42000): Invalid default value for 'create_date'

What is the error here?

Solution:

If you generated the script from the MySQL workbench. the following line is generated SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='TRADITIONAL,ALLOW_INVALID_DATES'; Remove TRADITIONAL from the SQL_MODE, and then the script should work fine

else, you could set the SQL_MODE as Allow Invalid Dates SET SQL_MODE='ALLOW_INVALID_DATES';.

Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more