Closed Sdoof closed 3 years ago
The milliseconds is not included in the price report, if you just need it for DB index, then you can put some sequence number in the millisecond field.
Thanks for the reply, one last thing, how to identify the first date & time (%m.%d.%Y %H:%M:%S) where tick data is HISTORICALLY available for the first time. In other words as of today how far back can I retrieve TICK data. At the moment I am using trial and error by changing the date_from argument, It would help if you could share the storage rules on your server and the date where those ticks are first available as of today?
you can check if tada is tick with:
history = fx.get_history(str_instrument, str_timeframe, date_from, date_to, quotes_count) currentunit, = ForexConnect.parse_timeframe(str_timeframe) if current_unit == fxcorepy.O2GTimeFrameUnit.TICK:
It seems there is timestamp bug when it comes to Tick, because the timestamp for each update is not set to milliseconds, only showing the seconds.
For example I currently get the following timestamps. 2019-06-24 19:13:43 2019-06-24 19:13:43 2019-06-24 19:13:43 2019-06-24 19:13:43 2019-06-24 19:13:43
Should be something like this. 2019-06-24 19:13:43.022 2019-06-24 19:13:43.053 2019-06-24 19:13:43.068 2019-06-24 19:13:43.070
This is a fairly critical bug because there is no way to eliminate 'out of order' ticks/updates, what is the best way to fix this?