Patients not being sent to centralized.mdb: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) Created page with "{{bug}} more info in Pagasa's email from Fri 2013-08-23 12:41 * 2013-08-22 - GRA/N3-SENT ON- 8/20/2013 12:44:15 PM Serial 9704 and 9710" |
Ttenbergen (talk | contribs) No edit summary |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{bug}} | {{Fixed bug}} | ||
Some records were not being added to centralized_data.mdb; should be fixed as per below. Please add discussion if not fixed. | |||
== log == | |||
more info in Pagasa's email from Fri 2013-08-23 12:41 | more info in Pagasa's email from Fri 2013-08-23 12:41 | ||
* 2013-08-22 - GRA/N3-SENT ON- 8/20/2013 12:44:15 PM Serial 9704 and 9710 | * 2013-08-22 - GRA/N3-SENT ON- 8/20/2013 12:44:15 PM Serial 9704 and 9710 | ||
** located backup with completed 9704 and 9710 | |||
** confirmed that send_centralized_1L_Log_update does '''not''' capture this patient (as it should not) Ttenbergen 10:27, 2013 August 29 (CDT) | |||
** confirmed that send_centralized_1L_Log_append '''does''' capture this patient (as it should not) Ttenbergen 10:27, 2013 August 29 (CDT) | |||
*** attempted to actually run the query, got key violation. | |||
*** the error happens because the current version of the L_Log table in centralized is keyed on Pat_ID and Location, where the queries now rely on D_ID. Updated centralized to ensure keys are filled, then imported into new centralized where the D_ID is an index that can not be left unfilled. Ttenbergen 10:51, 2013 August 29 (CDT) | |||
Latest revision as of 09:53, 29 August 2013
Some records were not being added to centralized_data.mdb; should be fixed as per below. Please add discussion if not fixed.
log
more info in Pagasa's email from Fri 2013-08-23 12:41
- 2013-08-22 - GRA/N3-SENT ON- 8/20/2013 12:44:15 PM Serial 9704 and 9710
- located backup with completed 9704 and 9710
- confirmed that send_centralized_1L_Log_update does not capture this patient (as it should not) Ttenbergen 10:27, 2013 August 29 (CDT)
- confirmed that send_centralized_1L_Log_append does capture this patient (as it should not) Ttenbergen 10:27, 2013 August 29 (CDT)
- attempted to actually run the query, got key violation.
- the error happens because the current version of the L_Log table in centralized is keyed on Pat_ID and Location, where the queries now rely on D_ID. Updated centralized to ensure keys are filled, then imported into new centralized where the D_ID is an index that can not be left unfilled. Ttenbergen 10:51, 2013 August 29 (CDT)