"Utilizing mongoDb's $set and $setOnInsert directives for updating specific fields within nested properties

Question

"Utilizing mongoDb's $set and $setOnInsert directives for updating specific fields within nested properties

I have a file containing sub-categories

{
  a: fire,
  b: {
    plane: fly,
    c: swim,
    d: jump,
  }
}

During upserts, I want to specifically change the "plane" category.

Here is what I have attempted:

const { categories, ...rest } = newRecord;
const updateCategories = categories;
delete updateCategories?.plane;
await Model.findOneAndUpdate(
{
  id: newRecord.id,
},
{
  $set: {
    ...rest,
    categories: updateCategories,
  },
  $setOnInsert: {
    "categories.plane": newRecord.plane,
  },
},
{
  upsert: true,
});

The error message I keep encountering is: Unable to update both categories and categories simultaneously. Even though I am removing the plane entry from the data being updated, referencing it through the categories field seems to cause confusion.

How can I rephrase this so that mongo understands my intention to only impact the "plane" sub-category within the categories, not the entire categories field in the $setOnInsert? Is there a way to indicate that an insert operation is taking place in the $set block for adding a conditional statement?

EDIT: It should be noted that I am utilizing documentDb on aws, which is believed to be built on mongo 4.0.

typescript mongodb aws-documentdb

Answer 1

Answer №1

After much searching, I finally found the solution detailed here on GitHub. The recommendation is to use the dotify function to handle certain scenarios.

export function dotify(obj: object) {
  const res: any = {};

  function recurse(obj: any, current?: string) {
    for (const key in obj) {
      const value = obj[key];
      const newKey = current ? current + "." + key : key;
      if (value && typeof value === "object" && !Array.isArray(value)) {
        recurse(value, newKey);
      } else {
        res[newKey] = value;
      }
    }
  }

  recurse(obj);
  return res;
}

  const { subproperties, ...rest } = newRecord;
  const updateProperties = subproperties;
  delete updateProperties?.aplus;
  await Model.findOneAndUpdate(
    {
      id: newRecord.id,
    },
    {
      $set: dotify({
        ...rest,
        subproperties: updateProperties,
      }),
      $setOnInsert: {
        "subproperties.aplus": newRecord.a,
      },
    },
    {
      upsert: true,
    }
  );

It appears that regular fields, including objects, are handled correctly when dotified. However, there seems to be an issue with how mongoose handles dotified arrays - they end up as undefined. This could possibly be related to schema configurations or limitations of the version of documentDb being used in AWS, which is based on an older version of MongoDB. It's worth checking if this has been addressed in newer versions.

Answer 2

After much searching, I finally found the solution detailed here on GitHub. The recommendation is to use the dotify function to handle certain scenarios.

export function dotify(obj: object) {
  const res: any = {};

  function recurse(obj: any, current?: string) {
    for (const key in obj) {
      const value = obj[key];
      const newKey = current ? current + "." + key : key;
      if (value && typeof value === "object" && !Array.isArray(value)) {
        recurse(value, newKey);
      } else {
        res[newKey] = value;
      }
    }
  }

  recurse(obj);
  return res;
}

  const { subproperties, ...rest } = newRecord;
  const updateProperties = subproperties;
  delete updateProperties?.aplus;
  await Model.findOneAndUpdate(
    {
      id: newRecord.id,
    },
    {
      $set: dotify({
        ...rest,
        subproperties: updateProperties,
      }),
      $setOnInsert: {
        "subproperties.aplus": newRecord.a,
      },
    },
    {
      upsert: true,
    }
  );

It appears that regular fields, including objects, are handled correctly when dotified. However, there seems to be an issue with how mongoose handles dotified arrays - they end up as undefined. This could possibly be related to schema configurations or limitations of the version of documentDb being used in AWS, which is based on an older version of MongoDB. It's worth checking if this has been addressed in newer versions.

"Utilizing mongoDb's $set and $setOnInsert directives for updating specific fields within nested properties

Answer №1

Similar questions

Leverage React components for efficient code reuse and export modules for

Is it secure to disclose the _id of a document in publication?

How to successfully utilize TypeScript ES6 modules and RequireJS for registering Angular elements

Incorporate my personalized icons into the button design of ionic 2 actionSheet

How can I apply conditions to the second element of a Number array with two elements in MongoDB?

I'm attempting to link up mongoDB with node.js, however I'm encountering an error in the terminal that says: "MongoAPIError: URI must contain hostname, domain name, and tld"

The mistake occurs when attempting to access a class property generated by a class constructor, resulting in a type error due to reading properties of

Issue with detecting undefined in a nested function using Typescript

Locate duplicate entries that are not null in MongoDB

Tips for having tsc Resolve Absolute Paths in Module Imports with baseUrl Setting

Discovering an element in an Array using Angular 2 and TypeScript

Executing double UpdateMany operations in MongoDB using $inc

Is it possible for RouteData in Angular 2 to transmit variables from a parent component to routed components?

Passing a class as a parameter in Typescript functions

How can I disable Typescript errors in VSCode for .JS / .JSX files while still keeping them for .TS / .TSX files?

Issue: property is not accessible on the current object in Angular 5

gulp-angular2 task is malfunctioning

Can you provide guidance on searching in mongoose using both $and and $or conditions?

Issue with ngAnimate in Angular 1.4 + TypeScript not functioning correctly upon initial page load

Encountering an issue with Nuxt 3.5.1 during the build process: "ERROR Cannot read properties of undefined (reading 'sys') (x4)"