[CSHARP-216] Add support for nolock option to MongoDatabase.Eval Created: 29/Apr/11  Updated: 02/Apr/15  Resolved: 29/Aug/11

Status: Closed
Project: C# Driver
Component/s: Feature Request
Affects Version/s: 1.0
Fix Version/s: 1.1

Type: New Feature Priority: Minor - P4
Reporter: Robert Stam Assignee: Robert Stam
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Add an overload to MongoDatabase.Eval with a boolean nolock parameter.



 Comments   
Comment by Robert Stam [ 29/Aug/11 ]

Created a new enum called EvalFlags and changed the Eval overload to use the new enum. This removes the ambiguity that existed with certain (admittedly rare) combinations of argument values.

Comment by Robert Stam [ 26/Aug/11 ]

Reopening this issue because the solution as implemented leads to ambiguities. Consider the following call:

database.Eval(
javascriptFunction,
new object[]

{ 1, 2, 3 }

,
true // is this a second argument to the javascript function or the nolock argument?
)

The solution will be to add an EvalFlags enum parameter which is used only to control Eval options and would never be an argument to the javascript function.

Comment by Robert Stam [ 14/Jun/11 ]

Implemented.

Generated at Wed Feb 07 21:36:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.