[SERVER-16779] kind of store / batch query procedure Created: 08/Jan/15 Updated: 09/Jan/15 Resolved: 09/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Usability |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | guipulsar | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
relating to my last post https://jira.mongodb.org/browse/SERVER-16735?filter=-2 If a kind of stored procedure was possible , it should solve this problematic, example: I put my blacklist items in another collections, great, Its possible if i can call localy (avoid post size pb) a procedure / batch querys were the first result query stored in a temp variable, then perform the second query. example: myprocedur(param,option){ //query1 //query2 Sorry for the long post but i think its very important problematic, there is actually no other solution to my pb, and im sure im not alone.. |
| Comments |
| Comment by Asya Kamsky [ 09/Jan/15 ] |
|
First time posters must be approved by the moderator, hence the delay. Your post is visible on google groups now. |
| Comment by guipulsar [ 09/Jan/15 ] |
|
so i posted to google group and my message was simply filtered..I guess the fact you have no options avaible to solve my status pb can explain that .. I have to say i'm very suprised because the non answers for a serious pb is anti profetional grade ..not serious at least.. |
| Comment by guipulsar [ 09/Jan/15 ] |
|
yes i understand, gona post in google group |
| Comment by Stennie Steneker (Inactive) [ 09/Jan/15 ] |
|
Hi, The SERVER project is for reporting bugs or feature suggestions for the MongoDB server. Given the related discussion in I appreciate your frustration that you cannot take the approach you intuit as correct, however trying to store unbounded data in a document is a definite performance and scaling anti-pattern. For more background see: Why shouldn't I embed large arrays in my documents?. Stored procedures will not solve the underyling schema challenges. If you can continue this discussion in the mongodb-user forum, hopefully we can arrive at a better understanding of your requirements and provide recommendations on how best to address these. Thanks, |