[jira] [Commented] (TC-382) If postinstall is run more than once it errors on one of the DB Inserts

["Hank Beatty (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TC-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16048230#comment-16048230 ] 

Hank Beatty commented on TC-382:
--------------------------------

I don't think this applies to 2.1.

in the _postinstall around line 698 the following INSERTS are run:

{{    insert into parameter (name, config_file, value) 
                values ('tm.url', 'global', '$tm_url') 
                ON CONFLICT DO NOTHING;

    insert into parameter (name, config_file, value) 
                values ('tm.infourl', 'global', '$tm_url/doc') 
                ON CONFLICT DO NOTHING;

    -- CRConfig.json parameters
    insert into parameter (name, config_file, value) 
                values ('geolocation.polling.url', 'CRConfig.json', '$tm_url/routing/GeoLite2-City.mmdb.gz') 
                ON CONFLICT DO NOTHING;

    insert into parameter (name, config_file, value) 
                values ('geolocation6.polling.url', 'CRConfig.json', '$tm_url/routing/GeoLiteCityv6.dat.gz') 
                ON CONFLICT DO NOTHING;
}}

The following doesn't seem to be applied in 2.0:

ALTER TABLE parameter ADD CONSTRAINT unique_param UNIQUE (name, config_file, value);

Once that is there the ON CONFLICT can be changed.

> If postinstall is run more than once it errors on one of the DB Inserts
> -----------------------------------------------------------------------
>
>                 Key: TC-382
>                 URL: https://issues.apache.org/jira/browse/TC-382
>             Project: Traffic Control
>          Issue Type: Bug
>          Components: Traffic Ops
>    Affects Versions: 2.0.0
>         Environment: CentOS 7.3
> PostgreSQL 9.6 (running on separate VM)
>            Reporter: Hank Beatty
>            Priority: Critical
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)