hi, I store a user's id in user_id,and I can populate the user to user_id but I wanna keep
user_id as the raw id and populate the user to another VIRTUAL fielf
field like 'user', how can I do that?
user_id as the raw id and populate the user to another VIRTUAL fielf
field like 'user', how can I do that?
@wxs77577 what do you mean by raw id ? Is user_id a bson ObjectID?
@lineus output like: {user_id: "asdf123asdf123fds", "user": {"_id": "asdf123asdf123fds", "nickname": "Johnny"}}
I don't wanna
populate modify user_id to an user object
I've found out on github. use
virtual
@wxs77577 take a look at http://mongoosejs.com/docs/populate.html#populate-virtuals
You'd define
user as a virtual and mark user_id as local_field.
@Pritilender yeah, now I use virtual field
Ok :)
Hey everyone! What is the most efficient / convenient way to retrieve a subdocument by another attribute than _id? Subdocuments have a ìsFeatured` flag, and I'd like to filter it sooner, than later.
@bybrunobarros use any other field that is indexed and query that field
@ytsruh Do you mean something like this (I haven't tried yet obviously)
parent.findOne({isFeatured: true})?
@bybrunobarros assuming you have indexed isFeatured then yes
if a field isnt indexed then the DB has to go through every record, an index is kind of like a snapshot of a field
so by going over every record it loses the 'effeciency' that you were looking for
Ok I didn't think about indexing boolean flags, I'll have a look. Maybe I'll filter afterward.
@ytsruh thanks
Hi guys, does anybody know the answer to my question here on Stackoverflow? https://stackoverflow.com/questions/49245949/mongoose-set-ref-on-loose-schema
@bybrunobarros no issues. An index will always be quicker than a standard query. But there are memory/performance downsides too remember
Yes, that's why I'm going to "have a look" :)
@microcipcip What's your schema definition? It looks ok to me to do what you want. Have you tried it out?
But am I able to populate without a for loop? I mean with
await db.page.findOne({ _id: myId }).populate('img')?
ATM I am in a Page schema and there I have a pageIds ObjectId from the Image schema
@microcipcip why not do one query and then map a new array?
So you mean I loop through it and populate manually?
From my understanding of Mongoose, I don't see why you couldn't do that single populate.
How does he know what collection to populate if there is no
ref?
That's why I asked you about your schema, I don't know what you have or not :D And why are you using
strict: false in the first place?
Ok I'll post it here
My pageSchema.... ignore validation rules
const pageSchema = schema(
joi.object({
title: joi.string().required(),
roles: joi.string().allow(''),
public: joi.boolean().required(),
slug: joi.string(),
published: joi.boolean().required(),
model: joi.string().required().meta({
type: 'ObjectId',
ref: 'Model'
}),
createdBy: joi.string().required(),
}),
{
strict: false,
timestamps: true,
minimize: false,
}
)
These are required fields, but I have many more that are added dinamically
how mare? 100 more or less than 10 more?
If I were in your place, I'd define every field upfront.
Basically it depend on the model
I have built a CMS
Depending on the model field it will change the number of fields there
so I could have image fields, textarea fields etc etc
take a look at this
you can state
ref there
but I don't know how good decision is going with this approach
But I can't set up the schema in the route AFAIK?
Imagine for example an express route
My approach to non-required fields is to define the whole model upfront, stating what is minimal required fields.
Umm ok
I guess the only solution I have is to loop through each property then
If the fields are not user generated, then I don't see why would you have any problem with stating what fields are possible. You could also use discriminated schema from Mongoose for even easier querying.
I have a Page model that changes from page to page
for example I may have a page with model
services and one with model portfolio
they will have different custom fields
have you successfully compiled a schema (mongoose.model()) defined this way @microcipcip ?
The only solution I have found so far is a for loop in the route
const pageObj = page.toJSON()
for (const field in pageObj) {
const fieldEl = pageObj[field]
if (fieldEl.type === 'imageEl') {
for (const [i, pageId] of fieldEl.pageIds.entries()) {
fieldEl.pageIds[i] = await db.image.findOne({ _id: pageId })
}
}
}
Yes because I have
strict: false
So I am allowed to add fields at will
#!/usr/bin/env node
'use strict'
const joi = require('joi')
const mongoose = require('mongoose')
const x = joi.object({
title: joi.string().required(),
roles: joi.string().allow(''),
public: joi.boolean().required(),
slug: joi.string(),
published: joi.boolean().required(),
model: joi.string().required().meta({
type: 'ObjectId',
ref: 'Model'
}),
createdBy: joi.string().required()
}, { strict: false })
const M = mongoose.model('test', x)
const m = new M({
title: '234',
roles: '234',
public: true,
slug: '234',
published: true,
model: '234',
createdBy: '234'
})
console.log(m)output:
gitter: ./wtf.js
/Users/lineus/dev/Help/mongoose5/node_modules/mongoose/lib/schema.js:602
throw new TypeError('Undefined type `' + name + '` at `' + path +
^
TypeError: Undefined type `undefined` at `isJoi`
Did you try nesting Schemas? You can only nest using refs or arrays.what am I doing wrong to make this work?
You can try without Joi I don't think it is necessary
I am using joigoose which is a plugin
interesting, didn't know that was a thing.
It is not related to my issue though
it's just a schema validator
yeah, I wasn't trying to solve your issue :) just lurk-learning.
Ah ok ;)
@kev can you look into my Issue
@lineus let me know if you need any additional info
Hey everyone! Is it possible to populate an embedded document?
await testimony[0].populate('org').execPopulate() is stalled. testimony[0] is an EmbeddedDocument. Am I missing something?
@bybrunobarros is
testimony[0] model or id?
@Pritilender I don't really understand the question 🤔 it's an embedded document. What do you mean? It's definitely not an id attribute.
I guess that
testimony is array of ids on some schema, so what am I asking is have you done MySchema.find({}).populate('testimony') or not?
@Pritilender Actually it's not an array of reference ids, they are "real" subdocuments.
oooh, ok
I'd like to populate only one testimony's org (testimony[0] in my example) and not all the testimonies' org.
I don't know if that's doable...
Maybe not. It's too bad if you can populate a document, but not a subdocument.
You can populate a subdocument, but I'm not sure if you can populate a particular subdocument.
Try
.populate('testimony.org')
It should work, but it will populate all
testimony subdocuments, and not just testimony[0]
Yes, I'd prefer not, but it's not really a big deal.
You can write a neat aggregation query with
$lookup stage which will take only first testimony and populate it
But that's more mongo approach, not mongoose
Well I'll think about all the solutions :)
thanks
Damn, I now get it what you want and what
testimony[0] is...
Yeah, it's weird if it's not possible to do
.populate on subdoc...
Sorry for the missunderstanding from my part.
No worries, it's more my explanation in a few words
@Pritilender Well finally I did this
testimony[0].org = await Org.findById(testimony[0].id)