slendium/ocd-conformance-tests
Watch
1
0
Fork
You've already forked ocd-conformance-tests
 0
Code Issues 5 Pull requests Projects Releases Packages Wiki Activity Actions

Test if write/upgrade commands leave options at defaults #3

New issue
Open
opened 2026-09-02 19:11:54 +02:00 by c.fahner · 0 comments
c.fahner commented 2026-09-02 19:11:54 +02:00
Owner
Copy link

Both the UpgradeCommand and WriteCommand define an "options" object. For consistency these options should be left at their constructor-defined defaults after the command is created.

For the UpgradeCommand:

  1. Call Database::enforceSchema()
  2. Test if the returned command has the default UpgradeOptions

For the WriteCommand:

  1. Call Collection::startInsert(), ::startUpdate(), ::startDelete()
  2. Test if the returned command has the default WriteOptions
Both the `UpgradeCommand` and `WriteCommand` define an "options" object. For consistency these options should be left at their constructor-defined defaults after the command is created. For the `UpgradeCommand`: 1. Call Database::enforceSchema() 1. Test if the returned command has the default `UpgradeOptions` For the `WriteCommand`: 1. Call Collection::startInsert(), ::startUpdate(), ::startDelete() 1. Test if the returned command has the default `WriteOptions`
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
slendium/ocd-conformance-tests#3
No description provided.