Attempt to modify Redmine issues table

I've copied the Redmine issues table from my test server over to a 2nd MariaDB server. Once I get things working, I'll apply those changes to my RM test server. Once I make sure THAT is working ok, I'll apply the changes to my RM production server.

You must execute the code again to save those values in the database.

CREATE TABLE Tree(
    nodeId INT NOT NULL PRIMARY KEY,
    parentNodeId INT NULL,
    name TEXT,
    FOREIGN KEY (parentNodeId) REFERENCES Tree(nodeId)
);

INSERT INTO Tree (nodeId, parentNodeId, name) VALUES
(1, NULL, 'Root A'),
(2, 1, 'Child A1'),
(3, 2, 'Child A11'),
(4, 2, 'Child A12'),
(5, 1, 'Child A2'),
(6, 5, 'Child A21'),
(7, 6, 'Child A211'),
(8, 6, 'Child A212'),
(9, 5, 'Child A22'),
(10, NULL, 'Root B'),
(11, NULL, 'Root C'),
(12, 11, 'Child C1'),
(13, 12, 'Child C11'),
(14, 12, 'Child C12'),
(15, 11, 'Child C2');

WITH RECURSIVE orderedTree (name, nodeId, depth, location)
AS
(
    SELECT
        name,
        nodeId,  
        0 AS depth,
        CAST(nodeId AS CHAR) AS location
    FROM Tree 
    WHERE parentNodeId IS NULL
 
    UNION ALL
 
    SELECT
        CONCAT(REPEAT(' ', parent.depth * 5), '|__', child.name), 
        child.nodeId, 
        parent.depth + 1,
        CONCAT(parent.location, '.', child.nodeId) AS location
    FROM Tree child
    INNER JOIN orderedTree parent
        ON child.parentNodeId = parent.nodeId
 
)
 
SELECT * FROM orderedTree
ORDER BY location;

name	nodeId	depth	location
Root A	1	0	1
\|__Child A1	2	1	1.2
\|__Child A11	3	2	1.2.3
\|__Child A12	4	2	1.2.4
\|__Child A2	5	1	1.5
\|__Child A21	6	2	1.5.6
\|__Child A211	7	3	1.5.6.7
\|__Child A212	8	3	1.5.6.8
\|__Child A22	9	2	1.5.9
Root B	10	0	10
Root C	11	0	11
\|__Child C1	12	1	11.12
\|__Child C11	13	2	11.12.13
\|__Child C12	14	2	11.12.14
\|__Child C2	15	1	11.15