maria-discuss team mailing list archive

[Roberto Spadim <roberto@xxxxxxxxxxxxx>]

please Reindl provide some data to test,
i found some information, we can add a bug at jira (bug tracker) of
mariadb and solve this problem... (if it exists...)

here one report from archlinux guys similar to your report, maybe we
(mariadb) have a problem with order by (?)
https://mailman.archlinux.org/pipermail/arch-general/2013-April/033282.html

here the create tables:
--------------------------------------------------------
CREATE TABLE IF NOT EXISTS `dbmail_mimeparts` (
  `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `hash` char(128) NOT NULL,
  `data` longblob NOT NULL,
  `size` bigint(20) NOT NULL DEFAULT '0',
  PRIMARY KEY (`id`),
  KEY `hash` (`hash`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
CREATE TABLE IF NOT EXISTS `dbmail_partlists` (
  `physmessage_id` bigint(20) unsigned NOT NULL DEFAULT '0',
  `is_header` tinyint(1) NOT NULL DEFAULT '0',
  `part_key` smallint(6) NOT NULL DEFAULT '0',
  `part_depth` smallint(6) NOT NULL DEFAULT '0',
  `part_order` smallint(6) NOT NULL DEFAULT '0',
  `part_id` bigint(20) unsigned NOT NULL DEFAULT '0',
  UNIQUE KEY `message_parts`
(`physmessage_id`,`part_key`,`part_depth`,`part_order`),
  KEY `physmessage_id` (`physmessage_id`),
  KEY `part_id` (`part_id`),
  CONSTRAINT `dbmail_partlists_ibfk_1` FOREIGN KEY (`physmessage_id`)
REFERENCES `dbmail_physmessage` (`id`) ON DELETE CASCADE ON UPDATE
CASCADE,
  CONSTRAINT `dbmail_partlists_ibfk_2` FOREIGN KEY (`part_id`)
REFERENCES `dbmail_mimeparts` (`id`) ON DELETE CASCADE ON UPDATE
CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
CREATE TABLE IF NOT EXISTS `dbmail_physmessage` (
  `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `messagesize` bigint(20) unsigned NOT NULL DEFAULT '0',
  `rfcsize` bigint(20) unsigned NOT NULL DEFAULT '0',
  `internal_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---