Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.5.8
-
None
Description
Hello guys,
we have a problem that could be very similar to the one mentioned in MDEV-17172.
When updating the charset of an empty backing table, we will no more get any results when calling the OQGRAPH table, i.e. every request returns an empty set.
It only happens in the following case:
# Create empty backing and oqgraph tables |
|
# Initially the result set is empty, which is expected |
SELECT * FROM graph; |
|
/*
|
This changes some varchar columns of the backing table to be a different CHARSET
|
and COLLATION. None of these columns are used in the graph table.
|
*/
|
ALTER TABLE backing CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; |
|
# Insert some data into backing table |
# INSERT INTO backing ... |
#
|
|
# Here it returns an empty result set |
SELECT * FROM graph; |
The error does not seem to happen, if we remove the first `
SELECT * FROM graph;` query, so for us it seems like the state of the database is cached (or something alike) in the state before the ALTER TABLE call and when later adding data, it is not reflected in the graph table.
Recreating the graph table or restarting the database server helped in 95% of the time.
Attachments
Issue Links
- relates to
-
MDEV-17172 ALTER TABLE on the base table of a OQGRAPH table leads to crash
- Confirmed