TradingView, Inc./TradingView

Keyboard shortcuts available
🔁
Want to see TradingView in your language? Join the translation team and help with the translations!

History

  1. Merge strategy for the requested data position. Requested barset is merged with current barset in the order of sorting bars by their opening time. This merge strategy can lead to undesirable effect of getting data from "future" on calculation on history. This is unacceptable in backtesting strategies, but can be useful in indicators.
    Merge strategy for the requested data position. Requested barset is merged with current barset in the order of sorting bars by their opening time. This merge strategy can lead to undesirable effect of getting data from "future" on calculation on history. This is unacceptable in backtesting strategies, but can be useful in indicators.

    Merge strategy for the requested data position. Requested barset is merged with current barset in the order of sorting bars by their opening time. This merge strategy can lead to undesirable effect of getting data from "future" on calculation on history. This is unacceptable in backtesting strategies, but can be useful in indicators.

    changed via the API .
    Copy to clipboard
  2. Merge strategy for the requested data position. Requested barset is merged with current barset in the order of sorting bars by their opening time. This merge strategy can lead to undesirable effect of getting data from "future" on calculation on history. This is unacceptable in backtesting strategies, but can be useful in indicators.
    Merge strategy for the requested data position. Requested barset is merged with current barset in the order of sorting bars by their opening time. This merge strategy can lead to undesirable effect of getting data from "future" on calculation on history. This is unacceptable in backtesting strategies, but can be useful in indicators.
    changed by Igorzimogorie .
    Copy to clipboard
  3.  
    changed by Igorzimogorie via a Batch Operation.
    Copy to clipboard
  4. 合併所請求數據位置的策略。請求的條形圖與當前的條形圖按照k線開放時間合併。這種合併策略可能導致從“future”獲取數據計算歷史的不良影響。這在回溯測試策略中不被接受，但可以用於指標。
    合併所請求數據位置的策略。請求的條形圖與當前的條形圖按照k線開放時間合併。這種合併策略可能導致從“future”獲取數據計算歷史的不良影響。這在回溯測試策略中不被接受，但可以用於指標。
    changed by Mark .
    Copy to clipboard
  5. 合併所請求數據位置的策略。請求的條形圖與當前的條形圖按照k線開放時間合併。這種合併策略可能導致從“未來”獲取數據計算歷史的不良影響。這在回溯測試策略中不被接受，但可以用於指標。
    合併所請求數據位置的策略。請求的條形圖與當前的條形圖按照k線開放時間合併。這種合併策略可能導致從“未來”獲取數據計算歷史的不良影響。這在回溯測試策略中不被接受，但可以用於指標。
    changed by Mark .
    Copy to clipboard
  6. 合併所請求數據位置的策略。請求的條形圖與當前的條形圖按照k線開放時間合併。這種合併策略可能導致從“未來”獲取數據計算歷史的不良影響。這在回溯測試策略中不被接受，但可以用於指標。
    合併所請求數據位置的策略。請求的條形圖與當前的條形圖按照k線開放時間合併。這種合併策略可能導致從“未來”獲取數據計算歷史的不良影響。這在回溯測試策略中不被接受，但可以用於指標。
    changed by Mark .
    Copy to clipboard