Bug 1261111 - RT-Gov 2.x database schema difference from 1.x schema
Summary: RT-Gov 2.x database schema difference from 1.x schema
Keywords:
Status: MODIFIED
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: RT Governance
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact: Matej Melko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-08 15:24 UTC by Julian Coleman
Modified: 2021-03-29 22:51 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RTGOV-666 0 Major Resolved Remove 'internal' field from DB schema 2016-02-11 09:18:10 UTC

Description Julian Coleman 2015-09-08 15:24:00 UTC 
RT-Gov 2.x has added the column:

    internal boolean,

in the `RTGOV_ACTIVITIES' table.  This is problematic:

  a change from the 1.x schema
  boolean is only supported by H2, MySQL, and PostgreSQL
Comment 1 Gary Brown 2015-09-09 13:12:18 UTC 
Proposal is to remove this field from the db schema, as it is only really used within ElasticSearch/Kibana to filter out internal services.

The benefit being that the db schema will not change, so no update/migration scripts required.
Comment 2 JBoss JIRA Server 2015-09-14 08:34:23 UTC 
Gary Brown <gary> updated the status of jira RTGOV-666 to Resolved
Comment 3 Gomathi Anandan 2015-09-14 15:07:02 UTC 
This issue has been resolved by engineering.Acking it for this release.
Note You need to log in before you can comment on or make changes to this bug.