Opened 6 years ago
Closed 5 years ago
#1942 closed improve feature (fixed)
Ensure that geonames_cache is up-to-date
Reported by: | shevek | Owned by: | shevek |
---|---|---|---|
Priority: | critical | Milestone: | 2.0 |
Component: | BW Geo | Keywords: | |
Cc: |
Description
As we rely on geonames as our service provider we need to ensure that our database is in sync with the original database.
Change History (8)
comment:1 Changed 6 years ago by shevek
- Component changed from unknown to BW Geo
- Owner set to shevek
- Priority changed from major to critical
- Status changed from new to assigned
- Type changed from unknown to improve feature
comment:2 Changed 6 years ago by shevek
- Milestone changed from unassigned to 1.6-proposed
I start working on this now. So I propose the fix for 1.6.
comment:3 Changed 6 years ago by shevek
- Milestone changed from 1.6-proposed to unassigned
Too complicated to fix for the geonames_cache table. Pushing to 1.7.
comment:4 Changed 6 years ago by shevek
- Milestone changed from unassigned to 1.9
comment:6 Changed 5 years ago by shevek
- Status changed from assigned to to_alpha
Fixed. Update process now tries to imports files for the last two days.
No test possible needs to be checked occasionally on the database.
comment:7 Changed 5 years ago by shevek
- Status changed from to_alpha to testing
comment:8 Changed 5 years ago by shevek
- Resolution set to fixed
- Status changed from testing to closed
Note: See
TracTickets for help on using
tickets.
This ticket is meant to keep to update the geonames_cache table with the content from geonames and check if the cron job to update the geonames_cache table actually works.