remove product_release_channels



a year ago
3 months ago


(Reporter: willkg, Unassigned)


(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)


We have two tables: product_build_types and product_release_channels. They have identical data in -prod:


breakpad=> select * from product_build_types;
    product_name     | build_type |        throttle        
 Firefox             | esr        | 1.00000000000000000000
 Fennec              | esr        | 1.00000000000000000000


breakpad=> select * from product_release_channels;
    product_name     | release_channel |        throttle        
 Firefox             | ESR             | 1.00000000000000000000
 Fennec              | ESR             | 1.00000000000000000000

The only difference is the column name (build_type vs. release_channel) and casing.

In the code are these notes:

Those are from 2014:

This bug covers switching everything to use product_build_types and removing product_release_channels which was deprecated in 2014.
Oh nice! Both tables are actively used but from various queries and stored procedures. 
If you normalize the release_channel/build_type column, the only actual difference between the two tables is:

▶ diff product_build_types.csv product_release_channels.csv
< TestProductAdrian,AURORA,1.0
< TestProductAdrian,BETA,1.0
< TestProductAdrian,ESR,1.0
< TestProductAdrian,NIGHTLY,1.0
< TestProductAdrian,RELEASE,1.0
> TestProductAdrian,RELEASE,1

Perhaps it'll be easier to decide which one to keep once we've deprecated more of the "crashes_per_*.sql" stuff. E.g.

One thing that bothers me is that the product_build_types table's build_type column is custom type (called `build_type`) whereas the product_release_channels is just a regular CITEXT type. Thus, it'd be nice to avoid custom types and instead keep product_release_channels (opposing the last paragraph in the bug description above).
Making this a P2 to do soon.
Priority: -- → P2
You need to log in before you can comment on or make changes to this bug.