mongoose populate array using skip and limit [duplicate]












0
















This question already has an answer here:




  • mongoDB array pagination

    1 answer



  • Mongoose populate virtual with sort and limit

    1 answer




Model is



const mongoose = require('mongoose')

const Schema = mongoose.Schema



var UserActivitySchema = new Schema({

    author: {type: mongoose.Schema.Types.ObjectId, required: true, unique: true, ref: 'user'},

    readHistory: [{articleid: {type: mongoose.Schema.Types.ObjectId, ref: 'article'}, date_read: {type: Date, default: Date.now()}}],

    watchHistory: [{videoid: {type: mongoose.Schema.Types.ObjectId, ref: 'video'}, date_watch: {type: Date, default: Date.now()}}],

    searchHistory: [{query: String, date:{type: Date, default: new Date()}}]

})



module.exports = mongoose.model('useractivity',UserActivitySchema, 'useractivities')


Here i want to fetch readHistory for which i have used query



   if (req.query.page) var page = parseInt(req.query.page);

else var page = 1;

UserActivity.findOne({author: req.client.userId}).select('readHistory')

.populate({path: 'readHistory.articleid', select: 'title description views thumbnailURI', options: { skip: (page-1)*10, limit: 10}, populate: {path: 'author', select: 'displayName -_id'}})

.exec().then(activity=>{

    if (!activity || activity.readHistory.length <= 0)

        res.json({success: false, message: 'You have not read any article yet.'})

    else {

        res.json({success: true, readHistory: activity.readHistory})

    }

}).catch(err=>{

    res.json({success: false, message: err.message})

})


but it returns all the document in the array.
How fix this?






node.js mongodb mongoose







share|improve this question













marked as duplicate by Neil Lunn mongodb
Users with the  mongodb badge can single-handedly close mongodb questions as duplicates and reopen them as needed.

StackExchange.ready(function() {
if (StackExchange.options.isMobile) return;

$('.dupe-hammer-message-hover:not(.hover-bound)').each(function() {
var $hover = $(this).addClass('hover-bound'),
$msg = $hover.siblings('.dupe-hammer-message');

$hover.hover(
function() {
$hover.showInfoMessage('', {
messageElement: $msg.clone().show(),
transient: false,
position: { my: 'bottom left', at: 'top center', offsetTop: -7 },
dismissable: false,
relativeToBody: true
});
},
function() {
StackExchange.helpers.removeMessages();
}
);
});
});
 Nov 19 '18 at 20:10


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.



















  • It's not the populate() that needs the "limit" here, but the "array". You instead $slice to project a "page" of items findOne({author: req.client.userId}).select({ 'readHistory': { '$slice': [ (page-1)*10, 10 ] }).populate(...) with everything except the options since the $slice is already there. The alternate case is about actually "limiting joins", which is a little more involved and not actually what populate() does, since it's not a "join" but another query retrieving data.

    – Neil Lunn
    Nov 19 '18 at 20:16











  • Missed a closing } in the select() of that example, but you should get the idea. Note also that the terms "skip" and "limit" are even used in the $slice documentation, since this was the original purpose of the operator way back in the original MongoDB design.

    – Neil Lunn
    Nov 19 '18 at 20:29
















0
















This question already has an answer here:




  • mongoDB array pagination

    1 answer



  • Mongoose populate virtual with sort and limit

    1 answer




Model is



const mongoose = require('mongoose')

const Schema = mongoose.Schema



var UserActivitySchema = new Schema({

    author: {type: mongoose.Schema.Types.ObjectId, required: true, unique: true, ref: 'user'},

    readHistory: [{articleid: {type: mongoose.Schema.Types.ObjectId, ref: 'article'}, date_read: {type: Date, default: Date.now()}}],

    watchHistory: [{videoid: {type: mongoose.Schema.Types.ObjectId, ref: 'video'}, date_watch: {type: Date, default: Date.now()}}],

    searchHistory: [{query: String, date:{type: Date, default: new Date()}}]

})



module.exports = mongoose.model('useractivity',UserActivitySchema, 'useractivities')


Here i want to fetch readHistory for which i have used query



   if (req.query.page) var page = parseInt(req.query.page);

else var page = 1;

UserActivity.findOne({author: req.client.userId}).select('readHistory')

.populate({path: 'readHistory.articleid', select: 'title description views thumbnailURI', options: { skip: (page-1)*10, limit: 10}, populate: {path: 'author', select: 'displayName -_id'}})

.exec().then(activity=>{

    if (!activity || activity.readHistory.length <= 0)

        res.json({success: false, message: 'You have not read any article yet.'})

    else {

        res.json({success: true, readHistory: activity.readHistory})

    }

}).catch(err=>{

    res.json({success: false, message: err.message})

})


but it returns all the document in the array.
How fix this?






node.js mongodb mongoose







share|improve this question













marked as duplicate by Neil Lunn mongodb
Users with the  mongodb badge can single-handedly close mongodb questions as duplicates and reopen them as needed.

StackExchange.ready(function() {
if (StackExchange.options.isMobile) return;

$('.dupe-hammer-message-hover:not(.hover-bound)').each(function() {
var $hover = $(this).addClass('hover-bound'),
$msg = $hover.siblings('.dupe-hammer-message');

$hover.hover(
function() {
$hover.showInfoMessage('', {
messageElement: $msg.clone().show(),
transient: false,
position: { my: 'bottom left', at: 'top center', offsetTop: -7 },
dismissable: false,
relativeToBody: true
});
},
function() {
StackExchange.helpers.removeMessages();
}
);
});
});
 Nov 19 '18 at 20:10


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.



















  • It's not the populate() that needs the "limit" here, but the "array". You instead $slice to project a "page" of items findOne({author: req.client.userId}).select({ 'readHistory': { '$slice': [ (page-1)*10, 10 ] }).populate(...) with everything except the options since the $slice is already there. The alternate case is about actually "limiting joins", which is a little more involved and not actually what populate() does, since it's not a "join" but another query retrieving data.

    – Neil Lunn
    Nov 19 '18 at 20:16











  • Missed a closing } in the select() of that example, but you should get the idea. Note also that the terms "skip" and "limit" are even used in the $slice documentation, since this was the original purpose of the operator way back in the original MongoDB design.

    – Neil Lunn
    Nov 19 '18 at 20:29














0












0








0









This question already has an answer here:




  • mongoDB array pagination

    1 answer



  • Mongoose populate virtual with sort and limit

    1 answer




Model is



const mongoose = require('mongoose')

const Schema = mongoose.Schema



var UserActivitySchema = new Schema({

    author: {type: mongoose.Schema.Types.ObjectId, required: true, unique: true, ref: 'user'},

    readHistory: [{articleid: {type: mongoose.Schema.Types.ObjectId, ref: 'article'}, date_read: {type: Date, default: Date.now()}}],

    watchHistory: [{videoid: {type: mongoose.Schema.Types.ObjectId, ref: 'video'}, date_watch: {type: Date, default: Date.now()}}],

    searchHistory: [{query: String, date:{type: Date, default: new Date()}}]

})



module.exports = mongoose.model('useractivity',UserActivitySchema, 'useractivities')


Here i want to fetch readHistory for which i have used query



   if (req.query.page) var page = parseInt(req.query.page);

else var page = 1;

UserActivity.findOne({author: req.client.userId}).select('readHistory')

.populate({path: 'readHistory.articleid', select: 'title description views thumbnailURI', options: { skip: (page-1)*10, limit: 10}, populate: {path: 'author', select: 'displayName -_id'}})

.exec().then(activity=>{

    if (!activity || activity.readHistory.length <= 0)

        res.json({success: false, message: 'You have not read any article yet.'})

    else {

        res.json({success: true, readHistory: activity.readHistory})

    }

}).catch(err=>{

    res.json({success: false, message: err.message})

})


but it returns all the document in the array.
How fix this?






node.js mongodb mongoose







share|improve this question















This question already has an answer here:




  • mongoDB array pagination

    1 answer



  • Mongoose populate virtual with sort and limit

    1 answer




Model is



const mongoose = require('mongoose')

const Schema = mongoose.Schema



var UserActivitySchema = new Schema({

    author: {type: mongoose.Schema.Types.ObjectId, required: true, unique: true, ref: 'user'},

    readHistory: [{articleid: {type: mongoose.Schema.Types.ObjectId, ref: 'article'}, date_read: {type: Date, default: Date.now()}}],

    watchHistory: [{videoid: {type: mongoose.Schema.Types.ObjectId, ref: 'video'}, date_watch: {type: Date, default: Date.now()}}],

    searchHistory: [{query: String, date:{type: Date, default: new Date()}}]

})



module.exports = mongoose.model('useractivity',UserActivitySchema, 'useractivities')


Here i want to fetch readHistory for which i have used query



   if (req.query.page) var page = parseInt(req.query.page);

else var page = 1;

UserActivity.findOne({author: req.client.userId}).select('readHistory')

.populate({path: 'readHistory.articleid', select: 'title description views thumbnailURI', options: { skip: (page-1)*10, limit: 10}, populate: {path: 'author', select: 'displayName -_id'}})

.exec().then(activity=>{

    if (!activity || activity.readHistory.length <= 0)

        res.json({success: false, message: 'You have not read any article yet.'})

    else {

        res.json({success: true, readHistory: activity.readHistory})

    }

}).catch(err=>{

    res.json({success: false, message: err.message})

})


but it returns all the document in the array.
How fix this?





This question already has an answer here:




  • mongoDB array pagination

    1 answer



  • Mongoose populate virtual with sort and limit

    1 answer







node.js mongodb mongoose




node.js mongodb mongoose






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 19 '18 at 16:30









auedbakiauedbaki

2516




2516




marked as duplicate by Neil Lunn mongodb
Users with the  mongodb badge can single-handedly close mongodb questions as duplicates and reopen them as needed.

StackExchange.ready(function() {
if (StackExchange.options.isMobile) return;

$('.dupe-hammer-message-hover:not(.hover-bound)').each(function() {
var $hover = $(this).addClass('hover-bound'),
$msg = $hover.siblings('.dupe-hammer-message');

$hover.hover(
function() {
$hover.showInfoMessage('', {
messageElement: $msg.clone().show(),
transient: false,
position: { my: 'bottom left', at: 'top center', offsetTop: -7 },
dismissable: false,
relativeToBody: true
});
},
function() {
StackExchange.helpers.removeMessages();
}
);
});
});
 Nov 19 '18 at 20:10


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.









marked as duplicate by Neil Lunn mongodb
Users with the  mongodb badge can single-handedly close mongodb questions as duplicates and reopen them as needed.

StackExchange.ready(function() {
if (StackExchange.options.isMobile) return;

$('.dupe-hammer-message-hover:not(.hover-bound)').each(function() {
var $hover = $(this).addClass('hover-bound'),
$msg = $hover.siblings('.dupe-hammer-message');

$hover.hover(
function() {
$hover.showInfoMessage('', {
messageElement: $msg.clone().show(),
transient: false,
position: { my: 'bottom left', at: 'top center', offsetTop: -7 },
dismissable: false,
relativeToBody: true
});
},
function() {
StackExchange.helpers.removeMessages();
}
);
});
});
 Nov 19 '18 at 20:10


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.















  • It's not the populate() that needs the "limit" here, but the "array". You instead $slice to project a "page" of items findOne({author: req.client.userId}).select({ 'readHistory': { '$slice': [ (page-1)*10, 10 ] }).populate(...) with everything except the options since the $slice is already there. The alternate case is about actually "limiting joins", which is a little more involved and not actually what populate() does, since it's not a "join" but another query retrieving data.

    – Neil Lunn
    Nov 19 '18 at 20:16











  • Missed a closing } in the select() of that example, but you should get the idea. Note also that the terms "skip" and "limit" are even used in the $slice documentation, since this was the original purpose of the operator way back in the original MongoDB design.

    – Neil Lunn
    Nov 19 '18 at 20:29



















  • It's not the populate() that needs the "limit" here, but the "array". You instead $slice to project a "page" of items findOne({author: req.client.userId}).select({ 'readHistory': { '$slice': [ (page-1)*10, 10 ] }).populate(...) with everything except the options since the $slice is already there. The alternate case is about actually "limiting joins", which is a little more involved and not actually what populate() does, since it's not a "join" but another query retrieving data.

    – Neil Lunn
    Nov 19 '18 at 20:16











  • Missed a closing } in the select() of that example, but you should get the idea. Note also that the terms "skip" and "limit" are even used in the $slice documentation, since this was the original purpose of the operator way back in the original MongoDB design.

    – Neil Lunn
    Nov 19 '18 at 20:29

















It's not the populate() that needs the "limit" here, but the "array". You instead $slice to project a "page" of items findOne({author: req.client.userId}).select({ 'readHistory': { '$slice': [ (page-1)*10, 10 ] }).populate(...) with everything except the options since the $slice is already there. The alternate case is about actually "limiting joins", which is a little more involved and not actually what populate() does, since it's not a "join" but another query retrieving data.

– Neil Lunn
Nov 19 '18 at 20:16





It's not the populate() that needs the "limit" here, but the "array". You instead $slice to project a "page" of items findOne({author: req.client.userId}).select({ 'readHistory': { '$slice': [ (page-1)*10, 10 ] }).populate(...) with everything except the options since the $slice is already there. The alternate case is about actually "limiting joins", which is a little more involved and not actually what populate() does, since it's not a "join" but another query retrieving data.

– Neil Lunn
Nov 19 '18 at 20:16













Missed a closing } in the select() of that example, but you should get the idea. Note also that the terms "skip" and "limit" are even used in the $slice documentation, since this was the original purpose of the operator way back in the original MongoDB design.

– Neil Lunn
Nov 19 '18 at 20:29





Missed a closing } in the select() of that example, but you should get the idea. Note also that the terms "skip" and "limit" are even used in the $slice documentation, since this was the original purpose of the operator way back in the original MongoDB design.

– Neil Lunn
Nov 19 '18 at 20:29












0






active

oldest

votes

















0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes

-

Popular posts from this blog

Guess what letter conforming each word

Image
6 $begingroup$ This is an entry in the Fortnightly Topic Challenge #41: Short and Sweet. 1 letter only could be mean anything . With an additional letter in front , could be used as medicine component and something you definitely learn or at least heard once. Add another letter in front , you would possibly hear that many times . Add an additional letter in front , you would found an independent country . With an additional letter, in the end , you would found something related to apple . Add another letter in the end , you would found something bad . Hint: Each letter is unique . word knowledge letters chemistry share | improve this question ...
Read more

Port of Spain

Image
For ports in the country of Spain, see List of ports in Spain. City in City of Port of Spain, Trinidad and Tobago Port of Spain City City of Port of Spain Top to bottom (left to right): Skyline of Port of Spain from Gulf of Paria; National Academy for the Performing Arts, Independence Square, Eric Williams Plaza; MovieTowne, Port of Port of Spain Motto(s):  "We Gather Strength As We Go Along" Port of Spain Coordinates: 10°40′N 61°31′W  /  10.667°N 61.517°W  / 10.667; -61.517 Coordinates: 10°40′N 61°31′W  /  10.667°N 61.517°W  / 10.667; -61.517 Country   Trinidad and Tobago Jurisdiction City of Port of Spain Settled 1560 Incorporated (town) 1853 Incorporated (city) 1914 Government  • Mayor Joel Martinez  • Governing body City Corporation Area [1]  • City 12 km 2 (5 sq mi) Elevation [2] 66 m (217 ft) Population (2011) [1]  • City 37,074  • Rank 3rd  • Density 3,090/km 2 (8,000/sq mi)...
Read more

Run scheduled task as local user group (not BUILTIN)

Image
0 I am trying to run a scheduled task with User Group (not a single user). This is working fine when I in the field "when running a task, use the following user account:" insert BUILTIN User Group (for example: Administrators or Users). But when I try it with the created Local User Group (example: TestGroup) it is not working. The Users in the TestGroup are the same as in the Administrators group. What could be the problem? Are there some restrictions to the Created User Group compared to BUILTINUsers? scheduled-tasks taskscheduler windowstaskschedule share | improve this question asked Nov 15 '18 at 15:36 Far...
Read more