Bug 749465

Summary: TopicIndex is hardcoded to use "Skynet" as DB name
Product: [Community] PressGang CCMS Reporter: Joshua Wulf <jwulf>
Component: Web-UIAssignee: Matthew Casperson <mcaspers>
Status: CLOSED NOTABUG QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.xCC: cbredesen, lcarlon, 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: 2011-11-07 04:19:03 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 Joshua Wulf 2011-10-27 06:44:03 UTC 
Right now we can point Skynet to a DB server other than the production one by editing the datasource in standalone.xml. This allows another server to be used.

However, it is not possible to change the name of the database. Whatever name you put, the app connects to the "Skynet" database.

Possibly the cause of this is line 36 of http://sourceforge.net/p/topicindex/code/197/tree/trunk/src/main/com/redhat/topicindex/entity/Category.java:

@Table(name = "Category", catalog = "Skynet", uniqueConstraints = @UniqueConstraint(columnNames =
 37 { "CategoryName" }))

Does the inclusion of the Catalog name override the datasource setting?
Comment 1 Matthew Casperson 2011-11-07 04:19:03 UTC 
Fixed in 20111107-1418

The catalog overrides the datasource, so with the catalog removed the datasource needs to specify the default database.