The b_timestamp type has public fields increment, timestamp, declared in the reverse order from the order that's widespread and natural: "timestamp, increment." This makes the driver itself and applications that use it error-prone. See CXX-1553 for an example of the problem and discussion of the solution.
- related to
-
CXX-1553 Wrong ctor call to b_timestamp
- Closed