Actually I have read this post, http://vendorsupport.paragonrels.com/... but no luck :(
I have posted this question on stackoverflow but found this forum instead so I will just post the stackoverflow link here.
RETS specification limits the millisecond to 1 digit so rounding happens.
So it would not be very helpful to do that.
If you need to reference a individual listing, it is best to do it by the unique KeyField value.
ah I get what you mean, so with datetime it's pretty much having + or - would be most use cases especially if I want to query in between date / datetime
Yes. Also when doing incremental updates it is best to have some timestamp overlap from the previous request to make sure you don't miss any updates.
thanks thanks for the advices :D I guess these are the questions I have for now. ^_^
Comments
Need your RETS login URL and account name (NO PASSWORD) before we can help.
Are you still having issues with this?
there's a reply on stackoverflow letting me know the encoding is incorrect that's why it's not out putting the
+and as for querying with millisecond, documentation doesn't seem to have anything about it as mentioned by the stackoverflow reply. So just want to confirm so if I want to query a record which has exact millisecond saved in db, is not possible then?