Sails.js find() date - node.js

The following queries return an empty array although my database has records in the given date.
Event.find({date: "2016-12-25"}).exec((err, holidays) => {
console.log(holidays);
}
let myDate = new Date(parameters.year,parameters.month,parameters.day);
Event.find({date: myDate}).exec((err, holidays) => {
console.log(holidays);
}
Anything I'm missing?

According to the documentation you could do it like so:
Model.find({ date: { '=': new Date('2/7/2014') } })

Related

Unable to query between dates in DynamoDB from NodeJS Lambda

I'm having some issues trying to query between dates for a dynamboDB table using NodeJS
I'm trying to query for the data in the data between the dates in the actualReadDate column and get these columns back: meterName, meterNumber, actualReadDate,actualReadTime
I've tried a few different things I've found online, latest attempt is below
async function scanForResults(){
try {
var params = {
TableName: 'MeterReadSubmission-dev',
keyConditionExpression : 'actualReadDate between :from and :to',
ProjectionExpression : 'meterName, meterNumber, actualReadDate,actualReadTime',
ExpressionAttributeValues: {
":from": startDate,
":to": endDate
}
};
var result = await docoClient.query(params).promise()
console.log("Retrieved data: ");
console.log(JSON.stringify(result))
} catch (error) {
console.error(error);
}
}
scanForResults()
The startDate and endDate variables are declared further above with the same format as the dates stored in DynamoDB
I looked at this link: Query DynamoDB between certain dates -NodeJs
But still just can't get it to work. Thanks in advance

Select all one day back but not older as one day

I try to use a Sequelize function to collect only table content that is older than today. But only for one day, not two days. As sample today
today: 2022/08/23
values only for: 2022/08/22 but not for 2022/08/21 and older.
For this is use:
checkDateBack: async function() {
return await dayins.findAll({
where: {
added_at: {
[Op.gte]: Sequelize.literal("DATE_SUB(CURDATE(), INTERVAL 1 DAY)"),
}
},
raw: true,
})
},
I have deleted all entries for 2022/08/22 in my temporary debug table but the result is 2022/08/21. In my idea of the function 2022/08/21 and older will get ignored.
So if I delete all entries for 2022/08/22 I expect an empty result.
Anything I did wrong with the function so it collects also 2 days old?
As I understood you need yesterday data, you need to get date range, use moment js for date
let date = new Date(); //suppose today is 2022/08/23
let endDate = moment(date).startOf("day").toString(); // starting of the day 12 am of(2022/08/23 )
let startDate = moment(date).subtract(1, "days").startOf("day").toString(); // starting of the day 12 am of(2022/08/22 )
// use [Op.between] insate of [Op.gte]
return await dayins.findAll({
where: {
added_at: {
[Op.between]: [startDate, endDate],
}
},
raw: true,
})
// it will return all data of 2022/08/22
// for sequelize createdAt if dont have any custome date fild
createdAt: {
[Op.between]: [startDate, endDate],
},

Cast error when using $gt ,$gte, $lt ,$lte in mongodb

I have a document like this
{
"_id":"5dfa6e23ef4b260e8c23a70c",
"username":"foo",
"count":4,
"log":[
{"description":"Eat sandwich","duration":30,"date":1576454400000,"_id":"5dfa6e49ef4b260e8c23a70e"},
{"description":"Eat sandwich","duration":300,"date":1576458700000,"_id":"5dfa6f1c2924c010b35c6b60"},
{"description":"Eat sandwich","duration":400,"date":1576459000000,"_id":"5dfa6f3a2924c010b35c6b61"},
{"description":"Eat sandwich","duration":400,"date":1576457400000,"_id":"5dfa6f702924c010b35c6b62"}
]
}
I'm trying to get the activities of a user's activities from a date range like this.
Activities.findOne({username:"foo",log:{date:{$gt: 1576454400000, $lt: 1576458700000 }}},function(err,activities){
//Do something
});
I always get a cast error whether the type is date or number. I have tried almost everything. I don't know what I'm doing wrong.
For the given input document in the post, the following query matches and returns the document (NOTE: in mongo shell).
This query uses $elemMatch:
db.test.findOne( { log: { $elemMatch: { date: { $gt: 1576454400000, $lte: 1576458700000 } } } } )
In case you do not use $elemMatch, the document field in the array must be specified using the dot (.) notation; e.g., "log.date".
db.test.findOne( { "log.date": { $gt: 1576454400000, $lte: 1576458700000 } } )
The query you are using will not give any syntax errors, but return wrong results.

How can change my field to hold an array of objects?

I am using mongodb to store the data.
I have a field "campus" to hold the ObjectIds of Campus data.
Intially the user had a single campus, but later on the type of campus had to be modified to hold an array of campus. But the initial records remained to be the same.
Now while I'm trying to push a new campusId, some records are not updating because of type change.
I have some 500 records in which some records have single objectId and in some records the campus is an array of ObjectIds.
Like this,
"campusIds" : ObjectId("5c8f304a4350a990f7c40")
And,
"campusIds" : [
ObjectId("5d136de2a02b2c14947652"),
ObjectId("5d136f0da02b2c14947656"),
ObjectId("5d137082a02b2c14947658"),
ObjectId("5d14520da02b2c1494765c"),
ObjectId("5d1459dd81801aef0865a8") ]
I cannot manaully change the records in mongodb as the records in large number.
Is there a way I can change the field to an array in my db?
Create a query which only filters documents where the field exists and it's of ObjectId type ($type 7). The results from this query can then be used to do a bulk update on the collection.
The following async operation does the above:
(async () => {
try {
const docs = await db.collection('collectionName').find({
'campus': {
'$exists': true,
'$type': 7
}
}).toArray()
const ops = docs.map(({ _id, campus }) => ({
'updateOne': {
'filter': { _id } ,
'update': { '$set': { 'campusIds': [campus] } }
}
}))
db.collection('collectionName').bulkWrite(ops)
} catch(err) {
// handle error
}
})()

MongoDB/Mongoose querying at a specific date?

Is it possible to query for a specific date ?
I found in the mongo Cookbook that we can do it for a range Querying for a Date Range
Like that :
db.posts.find({"created_on": {"$gte": start, "$lt": end}})
But is it possible for a specific date ?
This doesn't work :
db.posts.find({"created_on": new Date(2012, 7, 14) })
That should work if the dates you saved in the DB are without time (just year, month, day).
Chances are that the dates you saved were new Date(), which includes the time components. To query those times you need to create a date range that includes all moments in a day.
db.posts.find({ //query today up to tonight
created_on: {
$gte: new Date(2012, 7, 14),
$lt: new Date(2012, 7, 15)
}
})
...5+ years later, I strongly suggest using date-fns instead
import endOfDayfrom 'date-fns/endOfDay'
import startOfDay from 'date-fns/startOfDay'
MyModel.find({
createdAt: {
$gte: startOfDay(new Date()),
$lte: endOfDay(new Date())
}
})
For those of us using Moment.js
const moment = require('moment')
const today = moment().startOf('day')
MyModel.find({
createdAt: {
$gte: today.toDate(),
$lte: moment(today).endOf('day').toDate()
}
})
Important: all moments are mutable!
tomorrow = today.add(1, 'days') does not work since it also mutates today. Calling moment(today) solves that problem by implicitly cloning today.
Yeah, Date object complects date and time, so comparing it with just date value does not work.
You can simply use the $where operator to express more complex condition with Javascript boolean expression :)
db.posts.find({ '$where': 'this.created_on.toJSON().slice(0, 10) == "2012-07-14"' })
created_on is the datetime field and 2012-07-14 is the specified date.
Date should be exactly in YYYY-MM-DD format.
Note: Use $where sparingly, it has performance implications.
Have you tried:
db.posts.find({"created_on": {"$gte": new Date(2012, 7, 14), "$lt": new Date(2012, 7, 15)}})
The problem you're going to run into is that dates are stored as timestamps in Mongo. So, to match a date you're asking it to match a timestamp. In your case I think you're trying to match a day (ie. from 00:00 to 23:59 on a specific date). If your dates are stored without times then you should be okay. Otherwise, try specifying your date as a range of time on the same day (ie. start=00:00, end=23:59) if gte doesn't work.
similar question
You can use following approach for API method to get results from specific day:
# [HTTP GET]
getMeals: (req, res) ->
options = {}
# eg. api/v1/meals?date=Tue+Jan+13+2015+00%3A00%3A00+GMT%2B0100+(CET)
if req.query.date?
date = new Date req.query.date
date.setHours 0, 0, 0, 0
endDate = new Date date
endDate.setHours 23, 59, 59, 59
options.date =
$lt: endDate
$gte: date
Meal.find options, (err, meals) ->
if err or not meals
handleError err, meals, res
else
res.json createJSON meals, null, 'meals'
i do it in this method and works fine
public async getDatabaseorderbyDate(req: Request, res: Response) {
const { dateQuery }: any = req.query
const date = new Date(dateQuery)
console.log(date)
const today = date.toLocaleDateString(`fr-CA`).split('/').join('-')
console.log(today)
const creationDate = {
"creationDate": {
'$gte': `${today}T00:00:00.000Z`,
'$lt': `${today}T23:59:59.999Z`
}
};
`
``
Problem I came into was filtering date in backend, when setting date to 0 hour, 0 minute, 0 second, 0 milisecond in node server it does in ISO time so current date 0 hour, 0 minute, 0 second, 0 milisecond of client may vary i.e. as a result which may gives a day after or before due to conversion of ISO time to local timezone
I fixed those by sending local time from client to server
// If client is from Asia/Kathmandu timezone it will zero time in that zone.
// Note ISODate time with zero time is not equal to above mention
const timeFromClient = new Date(new Date().setHours(0,0,0,0)).getTime()
And used this time to filter the documents by using this query
const getDateQuery = (filterBy, time) => {
const today = new Date(time);
const tomorrow = new Date(today.getDate() + 1);
switch(filterBy) {
case 'past':
return {
$exists: true,
$lt: today,
};
case 'present':
return {
$exists: true,
$gte: today,
$lt: tomorrow
};
case 'future':
return {
$exists: true,
$gte: tomorrow
};
default:
return {
$exists: true
};
};
};
const users = await UserModel.find({
expiryDate: getDateQuery('past', timeFromClient)
})
This can be done in another approach using aggregate if we have timezoneId like Asia/Kathmandu
const getDateQuery = (filterBy) => {
const today = new Date();
const tomorrow = new Date(today.getDate() + 1);
switch(filterBy) {
case 'past':
return {
$exists: true,
$lt: today,
};
case 'present':
return {
$exists: true,
$gte: today,
$lt: tomorrow
};
case 'future':
return {
$exists: true,
$gte: tomorrow
};
default:
return {
$exists: true
};
};
};
await UserModel.aggregate([
{
$addFields: {
expiryDateClientDate: {
$dateToParts: {
date: '$expiryDate',
timezone: 'Asia/Kathmandu'
}
}
},
},
{
$addFields: {
expiryDateClientDate: {
$dateFromParts: {
year: '$expiryDateClientDate.year',
month: '$expiryDateClientDate.month',
day: '$expiryDateClientDate.day'
}
}
},
},
{
$match: {
expiryDateClientDate: getDateQuery('past')
}
}
])
We had an issue relating to duplicated data in our database, with a date field having multiple values where we were meant to have 1. I thought I'd add the way we resolved the issue for reference.
We have a collection called "data" with a numeric "value" field and a date "date" field. We had a process which we thought was idempotent, but ended up adding 2 x values per day on second run:
{ "_id" : "1", "type":"x", "value":1.23, date : ISODate("2013-05-21T08:00:00Z")}
{ "_id" : "2", "type":"x", "value":1.23, date : ISODate("2013-05-21T17:00:00Z")}
We only need 1 of the 2 records, so had to resort the javascript to clean up the db. Our initial approach was going to be to iterate through the results and remove any field with a time of between 6am and 11am (all duplicates were in the morning), but during implementation, made a change. Here's the script used to fix it:
var data = db.data.find({"type" : "x"})
var found = [];
while (data.hasNext()){
var datum = data.next();
var rdate = datum.date;
// instead of the next set of conditions, we could have just used rdate.getHour() and checked if it was in the morning, but this approach was slightly better...
if (typeof found[rdate.getDate()+"-"+rdate.getMonth() + "-" + rdate.getFullYear()] !== "undefined") {
if (datum.value != found[rdate.getDate()+"-"+rdate.getMonth() + "-" + rdate.getFullYear()]) {
print("DISCREPENCY!!!: " + datum._id + " for date " + datum.date);
}
else {
print("Removing " + datum._id);
db.data.remove({ "_id": datum._id});
}
}
else {
found[rdate.getDate()+"-"+rdate.getMonth() + "-" + rdate.getFullYear()] = datum.value;
}
}
and then ran it with mongo thedatabase fixer_script.js
Well a very simple solution to this is given below
const start = new Date(2020-04-01);
start.setHours(0, 0, 0, 0);
const end = new Date(2021-04-01);
end.setHours(23, 59, 59, 999);
queryFilter.created_at={
$gte:start,
$lte:end
}
YourModel.find(queryFilter)
So, the above code simply finds the records from the given start date to the given end date.
Seemed like none of the answers worked for me. Although someone mentioned a little hint, I managed to make it work with this code below.
let endDate = startingDate
endDate = endDate + 'T23:59:59';
Model.find({dateCreated: {$gte: startingDate, $lte: endDate}})
startingDate will be the specific date you want to query with.
I preferred this solution to avoid installing moment and just to pass the startingDate like "2021-04-01" in postman.

Resources