[Maria-discuss] verifying a table is using autogenerated PK or not
when I deleted a few rows, those rows did not get deleted on mariadb cluster second node. $ sudo grep "wsrep_certify_nonPK" /etc/mysql/my.cnf wsrep_certify_nonPK=1
| +-------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | uni12_jevents_vevdetail | CREATE TABLE `uni12_jevents_vevdetail` ( `evdet_id` int(12) NOT NULL AUTO_INCREMENT, `rawdata` longtext NOT NULL, `dtstart` int(11) NOT NULL DEFAULT '0', `dtstartraw` varchar(30) NOT NULL DEFAULT '', `duration` int(11) NOT NULL DEFAULT '0', `durationraw` varchar(30) NOT NULL DEFAULT '', `dtend` int(11) NOT NULL DEFAULT '0', `dtendraw` varchar(30) NOT NULL DEFAULT '', `dtstamp` varchar(30) NOT NULL DEFAULT '', `class` varchar(10) NOT NULL DEFAULT '', `categories` varchar(120) NOT NULL DEFAULT '', `color` varchar(20) NOT NULL DEFAULT '', `description` longtext NOT NULL, `geolon` float NOT NULL DEFAULT '0', `geolat` float NOT NULL DEFAULT '0', `location` varchar(120) NOT NULL DEFAULT '', `priority` tinyint(3) unsigned NOT NULL DEFAULT '0', `status` varchar(20) NOT NULL DEFAULT '', `summary` longtext NOT NULL, `contact` varchar(120) NOT NULL DEFAULT '', `organizer` varchar(120) NOT NULL DEFAULT '', `url` text NOT NULL, `extra_info` varchar(240) NOT NULL DEFAULT '', `created` varchar(30) NOT NULL DEFAULT '', `sequence` int(11) NOT NULL DEFAULT '1', `state` tinyint(3) NOT NULL DEFAULT '1', `modified` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `multiday` tinyint(3) NOT NULL DEFAULT '1', `hits` int(11) NOT NULL DEFAULT '0', `noendtime` tinyint(3) NOT NULL DEFAULT '0', PRIMARY KEY (`evdet_id`) ) ENGINE=InnoDB AUTO_INCREMENT=515 DEFAULT CHARSET=utf8 | +-------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ 1 row in set (0.00 sec) It seems that there's a PK. But what would cause this?
Just an idea: It could be because your PK-column is an int(12). An INT is an int(11) unless column length is defined otherwise specifically. An int(12) is unusual datatype (it does create however and returns the number formatted as a 12-character string as expected, so it is valid, it seems). But maybe such construction confuses Galera? -- Peter -- Webyog On Fri, Apr 17, 2015 at 10:58 AM, Umarzuki Mochlis <umarzuki@gmail.com> wrote:
participants (2)
-
Peter Laursen -
Umarzuki Mochlis