Bug 789170

Summary:	There are two entries for topic 5945 - Enable Role-Based Security for a RESTEasy JAX-RS Web Application
Product:	[Community] PressGang CCMS	Reporter:	Tom WELLS <twells>
Component:	Web-UI	Assignee:	Matthew Casperson <mcaspers>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	1.x	CC:	cbredesen, lcarlon, lnewson, topic-tool-list
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-02-20 04:01:53 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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.