Announcement

Collapse
No announcement yet.

Partner 728x90

Collapse

BUG/FEATURE NT7bXX: history work

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    BUG/FEATURE NT7bXX: history work

    It is translated from Russian by means of the program.
    -----------------------------------------------------

    Settings:
    (deleted AlexSTAL)


    1) Let's save up history for the instrument on which on server there is no history (deleted AlexSTAL)
    Let's choose "Reload All History Data":
    (deleted AlexSTAL)
    As a result all saved up history will leave:
    (deleted AlexSTAL)

    For instruments on which the history on server is inaccessible, it is impossible to delete the saved up history!

    2) The saved up history isn't used for tools with absent history on server (at the established parametre "Get data from server")
    (deleted AlexSTAL)

    If the instrument doesn't have history on server it should undertake from the saved up history (at the established parametre "Get data from server")!

    3) It is necessary to provide possibility of interdiction of occurrence of the messagedeleted AlexSTAL), for example so: (deleted AlexSTAL)
    Last edited by AlexSTAL; 08-07-2010, 01:00 AM.

    #2
    Hello AlexSTAL,

    I tested it on my end and I can reproduce this behavior as well. When reloading historical data or creating a new chart, it does not load the historical data saved in the database, but deletes it.

    I will forward your findings to our Development team as well as your suggestion at #3. Thank you for reporting.

    Comment


      #3
      Hello AlexSTAL,

      Unfortunately this is as expected behavior. When you download data for the Historical Data Manager, it will delete the old data. Subsequently new data is populated in the Historical Data Manager.

      If no new data is available at your data feed provider, unfortunately you will lose the old data as no new data is able to populate back in the Historical Data Manager.

      Comment


        #4
        So it is necessary to change this behaviour! To delete the data ONLY after their presence on server will prove to be true!

        Otherwise it turns out that the program is created not for the end user and as it is convenient to programmers!

        Comment


          #5
          The algorithm should be such:
          We request the data from historical server
          - If the data is, is deleted old from database and downloaded the new
          - If the data isn't present - that old isn't deleted!!!

          In each situation it is necessary to follow common sense!

          Comment


            #6
            I will forward your suggestion to our Development team and ask them if they can add this to the list of future considerations of the software.

            Thank you for your feedback.

            Comment

            Latest Posts

            Collapse

            Topics Statistics Last Post
            Started by Geovanny Suaza, 02-11-2026, 06:32 PM
            0 responses
            601 views
            0 likes
            Last Post Geovanny Suaza  
            Started by Geovanny Suaza, 02-11-2026, 05:51 PM
            0 responses
            347 views
            1 like
            Last Post Geovanny Suaza  
            Started by Mindset, 02-09-2026, 11:44 AM
            0 responses
            103 views
            0 likes
            Last Post Mindset
            by Mindset
             
            Started by Geovanny Suaza, 02-02-2026, 12:30 PM
            0 responses
            559 views
            1 like
            Last Post Geovanny Suaza  
            Started by RFrosty, 01-28-2026, 06:49 PM
            0 responses
            558 views
            1 like
            Last Post RFrosty
            by RFrosty
             
            Working...
            X