Hi.

There is no primary key in this table. I'm not sure if it is made in this way for something special but we get duplicated information in our database. We use mysql 5.0.

Thanks!

Comments

jjrosent’s picture

jjrosent commented

I believe this is by design, both the no key and the seemingly duplicate rows. If I understand casetracker correctly this is how casetracker implements the revision notification on comment updates. IE: when someone adds a comment and changes the case status from open to closed, casetracker in the theme view shows open >> closed in the comment. I think that data is sourced from this table.

jmiccolis’s picture

jmiccolis commented
Version: 5.x-1.3-beta1 » 6.x-1.x-dev
Status: Active » Fixed

@jjrosent you are exactly correct, at this point there should be two rows in the database for each comment.

To make things a bit better performing I've added an index to the casetracker_comment_status in the D6 branch. Setting to fixed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.