English subtitles

← Weather Table Columns Solution - Developing Android Apps

Get Embed Code
6 Languages

Showing Revision 10 created 05/25/2016 by Udacity Robot.

  1. All right, let's see how we did.
  2. If you checked record ID, weather
    condition ID, minimum temperature,
  3. wind speed, humidity,
    maximum temperature,
  4. date, weather direction and
    pressure, you've got this right.
  5. Now technically,
    one could have included either date or
  6. time, as time includes date.
  7. Month doesn't really
    make any sense here.
  8. But since we're really displaying the
    date, it makes sense for the database to
  9. actually replicate what's on
    the display as much as possible.
  10. Units should be stored in
    a separate table with preferences.
  11. There's no reason to store things
    we aren't displaying, such as,
  12. you know, rainfall or
    average temperature.
  13. And besides, we cannot get these
    from the OpenWeatherMap API.
  14. We do need weather condition ID,
    since we use this to
  15. both display the forecast, and
    determine the image to display.
  16. And finally,
    while it's not displayed in our UI,
  17. we need an ID column to
    uniquely identify each row.
  18. As discussed, it's required for
  19. all SQLI database tables that are going
    to be displayed in Android list views.