Update prefix_nodes_move_old_paths_after_update.sql

16e2c7fc623a2bdf883d882c6691debf632df6ba · bill2004158 · Feb 3, 2014 02:17

fix comment

+3 −3 · 1 file changed

sql/prefix_nodes_move_old_paths_after_update.sql +3 −3

diff --git a/sql/prefix_nodes_move_old_paths_after_update.sql b/sql/prefix_nodes_move_old_paths_after_update.sql
index 3ea44be..7cee8d6 100644
--- a/sql/prefix_nodes_move_old_paths_after_update.sql
+++ b/sql/prefix_nodes_move_old_paths_after_update.sql
@@ -9,9 +9,9 @@ CREATE
     TRIGGER `prefix_nodes_move_old_paths_after_update` AFTER UPDATE ON `prefix_nodes` 
     FOR EACH ROW BEGIN
     IF OLD.`parent_id` != NEW.`parent_id` THEN
-        //http://www.mysqlperformanceblog.com/2011/02/14/moving-subtrees-in-closure-table/
-        //in the example, when change node D's parent to B.
-        //its sql has only D & B. so I think it should currentNode.id& newParent.id
+        --http://www.mysqlperformanceblog.com/2011/02/14/moving-subtrees-in-closure-table/
+        --in the example, when change node D's parent to B.
+        --its sql has only D & B. so I think it should currentNode.id& newParent.id
         CALL p_prefix_nodes_move_old_paths_after_update(NEW.`id`, NEW.`parent_id`);
     END IF;