Skip to content
This repository has been archived by the owner on Feb 8, 2018. It is now read-only.

add schema and Python for countries #3999

Closed
wants to merge 2 commits into from

Conversation

chadwhitacre
Copy link
Contributor

@chadwhitacre chadwhitacre commented Apr 30, 2016

@chadwhitacre
Copy link
Contributor Author

Discovered in #4005 that the official country names aren't suitable for display. E.g., "United States of America (the)" should be "United States" or "the United States" depending on context.

@chadwhitacre
Copy link
Contributor Author

chadwhitacre commented May 2, 2016

Actually, it turns out that we already have good names in locale.countries ! 👍

So do we need the names in the countries table at all? Flags (788d92d), Babel, and pretty much everything I'm finding use the two-letter country codes. Should we simplify down to a single column? Will @kaguillera let us use the 2-letter country code as the primary—and only—key?

@kaguillera
Copy link
Contributor

Yes...that is cool if that is what everything uses

@chadwhitacre
Copy link
Contributor Author

Yes...that is cool if that is what everything uses

Hah! :D Well, on the other hand, this would mean updating all of the subsequent PRs that depend on country_id.

screen shot 2016-05-01 at 8 50 44 pm

@kaguillera
Copy link
Contributor

I would suggest that we do that now before we have to do that further down the line...is that difficult or too much work??

@chadwhitacre
Copy link
Contributor Author

@kaguillera I think we're okay with our own id field, and alpha-2 as a separate field. Do you see anything actively bad about that approach?

@chadwhitacre chadwhitacre modified the milestone: Bring Back Payroll for Team Gratipay May 4, 2016
@kaguillera
Copy link
Contributor

No...I am more inclined to that approach.

@chadwhitacre chadwhitacre force-pushed the symmetric-encryption branch from 8a22427 to da4cf0f Compare May 7, 2016 15:34
@chadwhitacre
Copy link
Contributor Author

Rebased on #3998 at 049bd48, previous head was fd1ca95.

@chadwhitacre
Copy link
Contributor Author

We can probably drop the name field and maybe even code3 since we'll be using code2 to index into Babel for names. We'll do the same for flags, and likely any other purpose in the foreseeable future. Holding name especially in our database seems redundant and confusing, since we're not actually using that data in the UI as one might expect.

@chadwhitacre
Copy link
Contributor Author

Okay, I roughed in #4008. We should look through that for insight on changes we may want to make here—it may make sense to use code2 more thoroughly after all.

@chadwhitacre
Copy link
Contributor Author

chadwhitacre commented May 11, 2016

Okay, removed name and code3 in 8a65cdf. We're not using name anywhere, and code3 was only used in the database. @kaguillera and I decided to keep the separate id field on principle. ☺️

We're using names from the Babel library, and we're not using code3.
@chadwhitacre
Copy link
Contributor Author

Remade as #4027.

@chadwhitacre chadwhitacre mentioned this pull request May 11, 2016
6 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants