search

microsoft / fhir-server

A service that implements the FHIR standard
MIT License
1.19k stars 510 forks source link

Negative versions #3840

Closed SergeyGaluzo closed 4 months ago

SergeyGaluzo commented 4 months ago

@mikaelweave in reference to https://github.com/microsoft/fhir-server/pull/3840#discussion_r1607359492

When customer specifies last updated, he/she takes control over versioning. Only if last updated is not specified, we can do checks on data content. If we do opposite, we can run into the problem, when according to current database state a record does not need to be written, but if other late arrivals come, it makes this decision invalid.

mikaelweave commented 4 months ago

@mikaelweave in reference to #3840 (comment)

When customer specifies last updated, he/she takes control over versioning. Only if last updated is not specified, we can do checks on data content. If we do opposite, we can run into the problem, when according to current database state a record does not need to be written, but if other late arrivals come, it makes this decision invalid.

I understand - if resources are imported specifying last updated, then we encounter scenarios where this is required. Since we import latest first (by last updated) in a batch, the latest one here takes version number 1.