Bug 789170 - There are two entries for topic 5945 - Enable Role-Based Security for a RESTEasy JAX-RS Web Application
Summary: There are two entries for topic 5945 - Enable Role-Based Security for a RESTE...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: PressGang CCMS
Classification: Community
Component: Web-UI
Version: 1.x
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Matthew Casperson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-10 00:48 UTC by Tom WELLS
Modified: 2015-05-18 01:26 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-20 04:01:53 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Tom WELLS 2012-02-10 00:48:39 UTC 
/Topic.xhtml

I was searching for the topic number for one of the topics I created yesterday (5945). When I found the topic, I discovered there were two entries for it, with the same topic ID.

Both Misty Stanley-Jones and Andrew Ross verified that there appeared to be two entries.

Not quite sure how this has happened.
Comment 1 Matthew Casperson 2012-02-10 01:02:27 UTC 
It's the same topic listed twice. This will be an issue with the search results screen.
Comment 2 Lee Newson 2012-02-16 00:08:37 UTC 
I found the reason why this topic is appearing twice. Topic is mapped to TopicSecondOrderData in a One to One Relationship. However there are two tuples in the TopicToTopicSecondOrderData table for this topic. How this occurred I'm unsure, but i'll look into it at some other point.

Also this appears to be the only topic that this should occur on.
Comment 3 Matthew Casperson 2012-02-20 02:16:50 UTC 
The foreign keys in the TopicToTopicSecondOrderData table were not set up correctly. The TopicID field was set to RESTRICT instead of CASCADE. That has been fixed, and the second row in the TopicToTopicSecondOrderData table for topic 5945 has been removed.
Note You need to log in before you can comment on or make changes to this bug.