OQGRAPH backing table changes not reflected in OQGRAPH table

Bug #1279246 reported by Ian Gilfillan on 2014-02-12
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OQGRAPH
Undecided
Unassigned

Bug Description

An update to the backing OQGRAPH table does not reflect when querying the OQGRAPH table. The change reflects after a server restart.

Running Ubuntu 12.04 32-bit. MariaDB 10.0.7 installed from standard package, 3.2.0-58-gerneric-pae kernel, dual CPU

How to repeat:

CREATE TABLE oq2_backing (
  origid INT UNSIGNED NOT NULL,
  destid INT UNSIGNED NOT NULL,
  weight DOUBLE NOT NULL,
  PRIMARY KEY (origid, destid),
  KEY (destid)
);

INSERT INTO oq2_backing(origid, destid, weight)
 VALUES (1,2,1), (2,3,1), (3,4,3), (4,5,1), (2,6,10), (5,6,2);

CREATE TABLE oq2_graph (
  latch VARCHAR(32) NULL,
  origid BIGINT UNSIGNED NULL,
  destid BIGINT UNSIGNED NULL,
  weight DOUBLE NULL,
  seq BIGINT UNSIGNED NULL,
  linkid BIGINT UNSIGNED NULL,
  KEY (latch, origid, destid) USING HASH,
  KEY (latch, destid, origid) USING HASH
)
ENGINE=OQGRAPH
data_table='oq2_backing' origid='origid' destid='destid' weight='weight';

UPDATE oq2_backing SET weight=4 WHERE origid=2 AND destid=6;

SELECT * FROM oq2_backing;
+--------+--------+--------+
| origid | destid | weight |
+--------+--------+--------+
| 1 | 2 | 1 |
| 2 | 3 | 1 |
| 2 | 6 | 4 |
| 3 | 4 | 3 |
| 4 | 5 | 1 |
| 5 | 6 | 2 |
+--------+--------+--------+

SELECT * FROM oq2_graph;
+-------+--------+--------+--------+------+--------+
| latch | origid | destid | weight | seq | linkid |
+-------+--------+--------+--------+------+--------+
| NULL | 1 | 2 | 1 | NULL | NULL |
| NULL | 2 | 3 | 1 | NULL | NULL |
| NULL | 2 | 6 | 10 | NULL | NULL |
| NULL | 3 | 4 | 3 | NULL | NULL |
| NULL | 4 | 5 | 1 | NULL | NULL |
| NULL | 5 | 6 | 2 | NULL | NULL |
+-------+--------+--------+--------+------+--------+

I have repeated the bug on another machine, Ubuntu 12.04 64-bit, both fairly standard my.cnf settings. The problem persists on 10.0.8.

Elena Stepanova (elenst) wrote :

See comments and suggested solution in https://mariadb.atlassian.net/browse/MDEV-5744

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers