TMP dates imported backwards

From CCMDB Wiki
Revision as of 15:52, 23 June 2014 by Ttenbergen (talk | contribs) (spinning out into own article)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

When we imported the TMP date var day and month got switched around for some, ie instead of April 1 it will be imported as January.

Solution

We will update the values in centralized_data.mdb with the proper values from TmpV2 1.mdb.

Spun this out into its own article since it will be a bulk update from query and we should have a record of what we did if we later find that anything went weird.

Question before go

Before go, I need to confirm: Template:Discussion

  • Pagasa, you are still keeping clean TmpV2 1.mdb, correct? If I update all date_vars from there we should have some for each record in centralized, as far as we know? Ttenbergen 15:52, 2014 June 23 (CDT)

Plan

  • link TmpV2 1.mdb table ' into Centralized data front end.mdb
  • confirm a record exists in TmpV2 for each entry in centralized and vice versa
    • query '
    • query '
  • run query fix_tmp_dates to update centralized from TmpV2

SQL for query fix_tmp_dates

Storing here for future reference as it will be removed from front end once done.