Skip to content

Update query.txt #856

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Update query.txt #856

wants to merge 1 commit into from

Conversation

MountainMan87119
Copy link

to facilitate noobs to either MongoDB or working in a Shell, toss in occassional added material to cover material that matters and can be addressed with minimal effort or space.

to facilitate noobs to either MongoDB or working in a Shell, toss in occassional added material to cover material that matters and can be addressed with minimal effort or space.
@ghost ghost assigned kay-kim Apr 13, 2013
@tychoish
Copy link
Contributor

Thanks for the contribution!

Could you please sign the MongoDB/10gen Contributor agreement:

http://www.10gen.com/legal/contributor-agreement

And I'll work to get this change merged into the documentation as quickly as possible.

Cheers,
sam

@MountainMan87119
Copy link
Author

Actually, I am not very impressed with Article/Item 3. I decline. It is
not explicit and concise and transparent what patent(s) are referred to...
logically, on the surface, one would assume "any patent that can be whipped
up from/as a result of" (some contribution) but ... not clear.

Besides, a simple permission to use the what, 2 or 3 lines of DOCUMENTATION
would take, in a sane world, like 1 line.

Ha, no this is not what I expected at all.

Love the product, respect the coders, but screw all that lawyer shit.

Enjoy a lovely spring!
Sincerely,
Bryan

On Tue, Apr 16, 2013 at 10:24 AM, Sam Kleinman [email protected]:

Thanks for the contribution!

Could you please sign the MongoDB/10gen Contributor agreement:

http://www.10gen.com/legal/contributor-agreement

And I'll work to get this change merged into the documentation as quickly
as possible.

Cheers,
sam


Reply to this email directly or view it on GitHubhttps://github.com//pull/856#issuecomment-16458693
.

@tychoish tychoish closed this Apr 16, 2013
@tychoish
Copy link
Contributor

Sorry about this. I've created the following ticket to track the addition of this kind of example.

https://jira.mongodb.org/browse/DOCS-1402

@MountainMan87119
Copy link
Author

Hello Sam,
Wow. Strong work. All the best. :)

It isn't that anybody is going to make something patentable out of
instructions for use, it is
the principle of making it easy to contribute, and you are all over that.
Respect.

B.

On Tue, Apr 16, 2013 at 12:10 PM, Sam Kleinman [email protected]:

Sorry about this. I've created the following ticket to track the addition
of this kind of example.

https://jira.mongodb.org/browse/DOCS-1402


Reply to this email directly or view it on GitHubhttps://github.com//pull/856#issuecomment-16465426
.

mongo-cr-bot pushed a commit that referenced this pull request Mar 24, 2022
* DOCSP-19054 inital scaffolding

* update to messaging

* moving query-api to root

* CR 1

* toc update

* tweak TOC again

* adjust query api position in TOC

* CR updates to query-api bullet list and more

* geoWithin update

* Additional feedback updates

* bolding bullet points

* removing atlas search

* update data transformations bullet

* TR1 Add materialized view bullet

* add document join support bullet

* remove the

* remove last blank
mongodb-server-docs-sync-bot bot pushed a commit that referenced this pull request Jun 23, 2025
* DOCSP-46527 -- Add GitHub access requirement note

* DOCSP-46527 -- copy review revision

(cherry picked from commit 8ef53b8)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants