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

ASF GitHub Bot commented on TC-15:
----------------------------------

GitHub user dneuman64 opened a pull request:

    https://github.com/apache/incubator-trafficcontrol/pull/26

    TC-15 - Fix seeds.sql to avoid foreign key error

    This closes #TC-15

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/dneuman64/incubator-trafficcontrol 
to-fix-seeds

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-trafficcontrol/pull/26.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #26
    
----
commit 3cf3191bd010900f723eaa76c57960580c2c1fb7
Author: Dave Neuman <[email protected]>
Date:   2016-10-31T21:38:19Z

    fix seeds.sql to check for correct data before insert.  This fixes TC-15

----


> Duplicate data in seeds.sql results in error
> --------------------------------------------
>
>                 Key: TC-15
>                 URL: https://issues.apache.org/jira/browse/TC-15
>             Project: Traffic Control
>          Issue Type: Bug
>          Components: Traffic Ops
>    Affects Versions: 1.8.0
>            Reporter: David Neuman
>            Assignee: David Neuman
>             Fix For: 1.8.0
>
>
> When you try to run a setup of the Traffic Ops database, it fails with the 
> following error:  ERROR 1452 (23000) at line 172: Cannot add or update a 
> child row: a foreign key constraint fails 
> (`to_integration`.`profile_parameter`, CONSTRAINT 
> `fk_atsprofile_atsparameters_atsparameters1` FOREIGN KEY (`parameter`) 
> REFERENCES `parameter` (`id`) ON DELETE CASCADE ON UPDATE NO ACTION)
> This is because of a copy/paste error on lines 152 and 153 that cause 
> duplicate data.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to