Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.3.18
-
None
-
Windows 7
Description
The global variable is set to log_warnings=0.
If the following SQL statement is executed a warning is still written into the errorlog:
CREATE TABLE `test_pending` (
|
`UniqueEventUnitID` int(11) NOT NULL,
|
`LMByHostName` varchar(255) DEFAULT '?',
|
`LMByHandlerName` varchar(80) DEFAULT '?',
|
`LMByZISUserID` varchar(80) DEFAULT '?',
|
`LMByUniqueID` int(11) DEFAULT 0,
|
`ModifyTime` datetime DEFAULT '2004-01-01 00:00:00',
|
`ModifyCounter` int(11) DEFAULT 0,
|
`CreateTime` datetime DEFAULT '2004-01-01 00:00:00',
|
`EraseTime` datetime DEFAULT '2004-01-01 00:00:00',
|
`EventUnitState` smallint(6) DEFAULT 0,
|
`UserDefinedEventUnitID` varchar(80) DEFAULT '',
|
`StateText` text DEFAULT NULL,
|
`ZISSourceDescData` blob DEFAULT NULL,
|
`ZISSourceOTypNr` int(11) DEFAULT 0,
|
`ZISSourceRBNr` int(11) DEFAULT 0,
|
`AcknowledgeFlag` tinyint(4) DEFAULT 0,
|
`RevisionFlag` tinyint(4) DEFAULT 0,
|
`RepeatCounter` int(11) DEFAULT 0,
|
`HelpFileName` varchar(255) DEFAULT '',
|
`HasEventUnitTMOAction` tinyint(4) DEFAULT 0,
|
`TMOActionDateTime` datetime DEFAULT NULL,
|
`TMOSetAcknowledgeFlag` tinyint(4) DEFAULT NULL,
|
`TMONewAcknowledgeFlag` tinyint(4) DEFAULT NULL,
|
`TMOSetRevisionFlag` tinyint(4) DEFAULT NULL,
|
`TMONewRevisionFlag` tinyint(4) DEFAULT NULL,
|
`TMOSetEventUnitState` tinyint(4) DEFAULT NULL,
|
`TMONewEventUnitState` smallint(6) DEFAULT NULL,
|
`TMOEventUnitTMOAction` tinyint(4) DEFAULT NULL,
|
`TMOREXXLabelStartActive` smallint(6) DEFAULT NULL,
|
`TMOREXXLabelName` varchar(80) DEFAULT NULL,
|
`TMOREXXLabelParams` text DEFAULT NULL,
|
`TMOREXXLabelStartBeforeEvtActn` smallint(6) DEFAULT NULL,
|
`ProductInterfaceType` tinyint(4) DEFAULT NULL,
|
`ProductInterfaceID` varchar(80) DEFAULT NULL,
|
`UniqueProductInterfaceEventID` varchar(255) DEFAULT NULL,
|
`CreatorZISSourceDescData` blob DEFAULT NULL,
|
`CreatorZISSourceOTypNr` int(11) DEFAULT NULL,
|
`CreatorZISSourceRBNr` int(11) DEFAULT NULL,
|
`Description` text DEFAULT NULL,
|
`EventAttributesDictionary` blob DEFAULT NULL,
|
`EventAttributes` longblob DEFAULT NULL,
|
`UserDefinedREXXLabelMenuName` varchar(80) DEFAULT NULL,
|
`AcknowledgeTime` datetime DEFAULT NULL,
|
`AcknowledgerZISSourceDescData` blob DEFAULT NULL,
|
`AcknowledgerZISSourceOTypNr` int(11) DEFAULT NULL,
|
`AcknowledgerZISSourceRBNr` int(11) DEFAULT NULL,
|
`DeleteTime` datetime DEFAULT NULL,
|
`DeleterZISSourceDescData` blob DEFAULT NULL,
|
`DeleterZISSourceOTypNr` int(11) DEFAULT NULL,
|
`DeleterZISSourceRBNr` int(11) DEFAULT NULL,
|
`EventRawDataType` int(11) DEFAULT NULL,
|
`EventRawData` longblob DEFAULT NULL,
|
PRIMARY KEY (`UniqueEventUnitID`),
|
KEY `NCI_test_P_UserDefID` (`UserDefinedEventUnitID`),
|
KEY `NCI_test_P_ModifyTime` (`ModifyTime`)
|
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
|
The MariaDB documentation says to log_warning = 0:
If set to 0, warnings are not logged.
https://mariadb.com/kb/en/library/error-log/#verbosity-level-0
https://mariadb.com/kb/en/library/server-system-variables/#log_warnings
Attachments
Issue Links
- relates to
-
MDEV-16969 Fix error message as promised in upstream Bug #69336
- Open
-
MDEV-19292 "Row size too large" error when creating table with lots columns when row format is DYNAMIC or COMPRESSED
- Closed
-
MDEV-20194 Warnings inconsistently issued upon CHECK on table from older versions
- Closed
-
MDEV-20400 Implement a way to query an InnoDB table's max row size
- Open
-
MDEV-20832 Don't print "row size too large" warnings in error log if innodb_strict_mode=OFF and log_warnings<=2
- Closed
-
MDEV-20949 Stop performing unnecessary maximum row size check for DML
- Closed
-
MDEV-22585 Incorrect note being written to the error log when CREATE and ALTER fail due to Row Size Too Large and in all cases for TRUNCATE and OPTIMIZE TABLE.
- Open
-
MDEV-23521 Implement an InnoDB row format that can use overflow pages for smaller columns
- Open