I think this case is the measurement error resulting collision between dividendRetrieval and splitDetectByQuandl script. After checking the database dated 09.07.2015 and 10.07.2015, I can guess what happened as follows:
- When the script dividendRetrieval run: it will take the value of date_ex in product_dividend_trigger de update for special_date_update and special_date_last of 07/08/2015 and delete all product_price_adjusted. But after dividendRetrieval script is running, the script is run splitDetectByQuandl start, because then the script has not finished running dividendRetrieval up and special_date_last special_date_update value remains the value of (special_date_last: 2001-05-04 and special_date_update: 2015-07 -07), it will be the case taken from the product_price price for product_price_adjusted according to special_date_update special_date_update day plus 40 days. Once finished it will cost only 1 day is on 07.07.2015 and at the same time it is updated again special_date_update while 2015-07-07 2015-07-08 special_date_last is updated.
=> For larger special_date_last special_date_update so will not be calculated prices in the next time (time code is checked in the condition that special_date_update> special_date_last or special_date_last = special_date_update). * workarounds: before running the script, you should check script dividendRetrieval splitDetectByQuandl Are run or not. If the script is running, we should dividendRetrieval to script splitDetectByQuandl run next time. Because the script is run 1 time dividendRetrieval at 4am daily. But the script is run 5p splitDetectByQuandl 1 times.
đang được dịch, vui lòng đợi..