Server-side Code Execution

[Ethan Gunderson]

This is more of a curiosity question than anything, but what are you guys using Server-Side code execution for? And by that, I mean in the context of:

db.myCollection.find( { $where: "this.a > 3" });

It makes a lot of sense that, behind the scenes, this is what the query operators are using, but other than that, what are you using this feature for? Was this designed to solve a specific problem, or is it just a byproduct of implementing query operators?

--
Ethan

http://www.mongodb.org/display/DOCS/Server-side+Code+Execution

[Markus Gattol]

> Was this designed to solve a specific problem, or is
> it just a byproduct of implementing query operators?

I would say neither. Semantically it's the same as stored
procedures ... more or less.

[Eliot Horowitz]

Actually that's not used internally at all since it's slower than the query operator

Also, it's designed exactly not to solve a specific problem but a general one. 

Its basically meant to fill gaps in the query language since it's still evolving

--
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To post to this group, send email to mongod...@googlegroups.com.
To unsubscribe from this group, send email to mongodb-user...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/mongodb-user?hl=en.

[Scott Hernandez]

I would argue this is very little like a stored procedure and
shouldn't be treated as such (or thought of that way). Stored
procedures don't have the byproduct they are single threaded (across
the server, like javascript is). Stored procedures aren't executed on
a single row (that is usually called a user-function), but more like a
full query which returns values (rows).

[Ethan Gunderson]

Thanks Eliot, that makes sense. Guess that's what I get for jumping the gun and assuming query operators used it.