Question: any reason to check that new entry timestamp is newer than previous? about flashdb

[armink]

Because the FlashDB uses the binary search algorithm to search TSDB. The search will cause problems when timestamp cannot keep incrementing.

[valkuc]

If the binary search is used just for iteration functions then what about make this feature less restrictive? I see few options:

1. Allow to save such values and print warning message like "The saved timestamp is before the last saved entry - the search functions may work incorrectly"
2. Add configuration option (#define) to disable timestamp check. This option should be well commented, with information that enabling this option can break up searching functionality if newly saved item timestamp is lesser than previous, use it at your own risk.

[armink]

If you know it's wrong, why do you do it?

[valkuc]

Well, this will work if it's necessary just to display last 100 saved records. Also this will prevent situations like I described in my first message - when the date was changed to the future and then changed back. Because there is no functionality to delete specific TSDB record it can lead to a deadlock - you will not be able to save anything until you either clean whole partition or wait until your actual date will be greater than last saved.