You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by "Jeremy Mitchell (JIRA)" <ji...@apache.org> on 2017/02/01 17:51:51 UTC
[jira] [Commented] (TC-126) Seeded data represented as a migration
was lost
[ https://issues.apache.org/jira/browse/TC-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15848705#comment-15848705 ]
Jeremy Mitchell commented on TC-126:
------------------------------------
This was brought to my attention thru this email:
https://lists.apache.org/thread.html/788c1ee4af7949c4130dc8d8c9939e05ab143c3c66edfe4619b3ce35@%3Cdev.trafficcontrol.apache.org%3E
> Seeded data represented as a migration was lost
> ------------------------------------------------
>
> Key: TC-126
> URL: https://issues.apache.org/jira/browse/TC-126
> Project: Traffic Control
> Issue Type: Bug
> Components: Traffic Ops
> Affects Versions: 2.0.0
> Reporter: Jeremy Mitchell
> Assignee: Jeremy Mitchell
> Fix For: 2.0.0
>
>
> The move from 1.8.x (mysql) to 2.0.x (postgres) involved rolling all the changes represented in the migration files into the create_tables.sql file and removing the migration files leaving only migration files that reflect schema changes after 1.8.
> However, some of these migration files included "seed data" or inserts which would not be captured in create_tables.sql.
> For example, the "ANY_MAP" delivery service type was lost as well as job agent and job status entries required for content invalidation.
> Need to go thru each deleted migration file to find seed data and move it to seeds.sql
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)