Data registration fails when specifying the time. What could be the reason for this?
This issue often arises due to “percent encoding not occurring at the + part when specifying the time”. However, be aware that some applications in use will perform percent encoding automatically.
When registering resource data with $date specified, how is data stored when registering two lots of resource data in a row with the same time set? In addition, when sending two lots of resource data without $date specified, is this data registered with different registration timestamps, that is, without registering the same record (same registration timestamp)?
When registering two lots of JSON data in a row with the same time specified, both data entities are registered. When two consecutive requests are sent without specifying the date, these are registered with a different timestamp when the interval between the requests sent is 1 ms or more. When this interval is under 1 ms, both requests will be registered with the same timestamp.
However, when specifying the same time for binary data, any data written beforehand will be overwritten with the newly written data.