TMP dates imported backwards: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
spinning out into own article
 
m Text replacement - "Category:All Legacy Projects" to "Category:Legacy project data"
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{bug}}
{{fixed bug}}
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.  
will be addressed by [[Re-import of TmpV2 data from Julie's Export 2014-09-08]]
 
----
 
 
When we imported the TMP date var day and month got switched around for some, i.e. instead of April 1 it will be imported as January 4.
Pagasa has continued to keep tmpV2_1.mdb up to date so we can get proper values from there.  


== Solution ==
== Solution ==
Line 6: Line 12:


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.
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:
{{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 ==
== Plan ==
* link [[TmpV2 1.mdb]] table '''' into [[Centralized data front end.mdb]]
* link [[TmpV2 1.mdb]] table '''' into [[Centralized data front end.accdb]]
* confirm a record exists in TmpV2 for each entry in centralized and vice versa
* confirm a record exists in TmpV2 for each entry in centralized and vice versa
** query ''''
** query ''''
Line 22: Line 23:
Storing here for future reference as it will be removed from front end once done.
Storing here for future reference as it will be removed from front end once done.


[[Category:All Projects]]
[[Category:Legacy project data]]

Latest revision as of 00:22, 3 January 2019


will be addressed by Re-import of TmpV2 data from Julie's Export 2014-09-08



When we imported the TMP date var day and month got switched around for some, i.e. instead of April 1 it will be imported as January 4. Pagasa has continued to keep tmpV2_1.mdb up to date so we can get proper values from there.

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.

Plan

SQL for query fix_tmp_dates

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