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

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

GitHub user mitchell852 opened a pull request:

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

    experimental TOv2 UI - changes to handle ints (postgres) instead of 
strings..

    ..for a deliveryservice
    
    jira - https://issues.apache.org/jira/browse/TC-4

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

    $ git pull https://github.com/mitchell852/incubator-trafficcontrol tov2-ui

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

    https://github.com/apache/incubator-trafficcontrol/pull/8.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 #8
    
----
commit 930763caedc750169e0ab1480d9bac47d5236619
Author: Jeremy Mitchell <[email protected]>
Date:   2016-10-20T19:40:27Z

    changes to handle ints (postgres) instead of strings

----


> TOv2 experimental UI should be compatible with Postgres - deliveryservice form
> ------------------------------------------------------------------------------
>
>                 Key: TC-4
>                 URL: https://issues.apache.org/jira/browse/TC-4
>             Project: Traffic Control
>          Issue Type: Bug
>          Components: Traffic Ops, Traffic Ops API
>    Affects Versions: 1.8.0
>            Reporter: Jeremy Mitchell
>            Assignee: Jeremy Mitchell
>            Priority: Minor
>
> The TOv2 experimental UI should be compatible with Postgres and as such it 
> should expect ints to be returned where the column's database type is an int. 
> rather than an int wrapped in a string like it was in mysql.
> In particular, this bug happens on the deliveryservice form page because I 
> have hardcoded references to string values.



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

Reply via email to