Closed (outdated)
Project:
Drupal core
Version:
6.x-dev
Component:
node system
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
5 Nov 2008 at 13:59 UTC
Updated:
2 Mar 2016 at 22:18 UTC
Jump to comment: Most recent
Hi,
Just a suggestion...
I was wondering why this module still uses node_comment_statistics.
The nodetype aspects already holds latest update and creation fields, like other nodetypes use.
So why not get loose from node_comment_statistics.
- The code uses lots of resources because for every node it seems that the (node)comment code touches the table. There is a thread about this to alter the code for drupal 7, but untill now the code takes lots of resources
- Because nodecomment is NOT a comment.module, but more a nodetype drupal module, it will be good to use nodetype aspects to show latest update etc..
Thank you for considering this!
greetings,
Martijn
Comments
Comment #1
balabushka commentedI am about importing data from an old forum software and I wondered about node_comment_statistics, too...
Comment #2
mlncn commentedWe have a site that was upgraded from 5 to 6, don't know if that's why, but we do not have a node_comment_statistics table. Thing is, we wouldn't need that table if it weren't for a handful of lines in node.module's search integration:
Can't figure out how this problem doesn't seem to have come up before, this dependency on a comment module table is very strange.
There's something of a core issue to get rid of it-- merging it into node module.
benjamin, agaric