[TC-102] API changes to reflect true datatypes

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.0.0
• Component/s: Traffic Ops, Traffic Ops API
• Labels: postgres
• Assignee: Jeremy Mitchell
• Reporter: Jeremy Mitchell
• Created: 18/Jan/17 18:01
• Updated: 16/Aug/17 03:24
• Resolved: 21/Feb/17 19:49

Description

With the move from MySQL to Postgres, the API will reflect the true data types of each value as represented in the database. For example, the Postgres version of the TO database now has boolean columns (rather than using smallint). These values should be represented in the API as booleans (true|false) as opposed to "0"|"1" as before.

Also, in the old MySQL TO, ints or numbers were represented as "age":"23" in the API. That should change to "age":23

These are the datatypes available in json and they should be taken advantage of when possible:

Boolean: true|false
String: double-quoted Unicode with backslash escaping
Number: double- precision floating-point format
Array: an ordered sequence of values
Object: an unordered collection of key:value pairs
Null

I'm creating this issue as a catch-all for any changes required to reflect the true data types in the api.

Issue Links

• relates to: TC-103 GET /update/:host_name should return boolean values