thread path format in database ruined after update from 6.x-1.x
tuffnatty - September 28, 2009 - 09:54
| Project: | Node comments |
| Version: | 6.x-2.0-beta1 |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | active |
Description
Hi,
After updating the site to 6.x-2.0-beta1, and posting some new comments into earlier existing threads, the thread column in node_comments table contains values of wrong format:
select nc.cid,nc.pid,nc.nid,nc.thread,n.created from node_comments nc left join node n on (nc.cid=n.nid) where nc.nid=4887 order by created;
+------+------+------+--------+------------+
| cid | pid | nid | thread | created |
+------+------+------+--------+------------+
| 4888 | 0 | 4887 | 01/ | 1253531414 |
| 4889 | 0 | 4887 | 02/ | 1253538025 |
| 4890 | 0 | 4887 | 03/ | 1253566662 |
| 4891 | 0 | 4887 | 04/ | 1253586436 |
| 4892 | 0 | 4887 | 6 | 1253596160 | /* this is the first wrong thread path */
| 4893 | 4890 | 4887 | 03.00/ | 1253596293 | /* this one looks OK, not top-level */
| 4894 | 0 | 4887 | 1 | 1253597248 | /* This is the next wrong thread path, calculated by "incrementing" the previous wrong path */
...I clearly see the problem in database, but don't see well where it is in code.
Currently I have manually downgraded to 6.x-1.x and manually fixed the database.