-
Type: Task
-
Resolution: Unresolved
-
Priority: Unknown
-
None
-
Component/s: Extended JSON
-
None
-
Needed
-
Summary
Test encoding dates after year 9999 with Relaxed Extended JSON
Motivation
Who is the affected end user?
Users encoding BSON to Relaxed Extended JSON.
How does this affect the end user?
Gives possibly non-portable encoding for obscure use of BSON date.
How likely is it that this problem or use case will occur?
I expect unlikely. CDRIVER-5759 was discovered internally. I expect needing to represent dates past year 9999 is an uncommon need.
If the problem does occur, what are the consequences and how severe are they?
Possible errors using non-portable encoding between MongoDB products.
Is this issue urgent?
No.
Is this ticket required by a downstream team?
No.
Is this ticket only for tests?
Yes, unless the test reveals a driver bug (like CDRIVER-5759)
Acceptance Criteria
Add a test to ensure encoding dates past year 9999 with Relaxed Extended JSON are as expected.
- is testing
-
CDRIVER-5759 Encoding of dates after year 9999 disagree with spec
- Closed
- split to
-
RUBY-3556 Test encoding dates after year 9999 with Relaxed Extended JSON
- Backlog
-
CSHARP-5340 Test encoding dates after year 9999 with Relaxed Extended JSON
- Backlog
-
GODRIVER-3379 Test encoding dates after year 9999 with Relaxed Extended JSON
- Backlog
-
JAVA-5652 Test encoding dates after year 9999 with Relaxed Extended JSON
- Backlog
-
NODE-6439 Test encoding dates after year 9999 with Relaxed Extended JSON
- Backlog
-
PYTHON-4884 Test encoding dates after year 9999 with Relaxed Extended JSON
- Backlog
-
RUST-2057 Test encoding dates after year 9999 with Relaxed Extended JSON
- Backlog
-
CDRIVER-5760 Test encoding dates after year 9999 with Relaxed Extended JSON
- Closed
-
CXX-3122 Test encoding dates after year 9999 with Relaxed Extended JSON
- Closed
-
MOTOR-1377 Test encoding dates after year 9999 with Relaxed Extended JSON
- Closed
-
PHPC-2471 Test encoding dates after year 9999 with Relaxed Extended JSON
- Closed