Datastore selection for Archive model

[TimurK]

Node version: v18.16.0 Sails version (sails): 1.5.8 ORM hook version (sails-hook-orm): 4.0.2 Organics hook version (sails-hook-organics): 2.2.2 Grunt hook version (sails-hook-grunt): 5.0.0 DB adapter & version (): sails-postgresql@5.0.1 DB adapter & version (): sails-mongo@2.0.1

---

I have default datastore which is uses sails-postgresql adapter and most of my Models uses this default datastore.

  // config/datastores.js

  default: {
    adapter: require('sails-postgresql'),
    url: 'postgresql://user:pass@postgres:5432/devdefaultdb',
  }

// models/PostgresModel.js

module.exports = {

  attributes: {

    mypostgresattribute: {
      type: 'string',
      required: true,
    },

  },

};

Also i have additional sails-mongo datastore and one model in it. Datastore for this model configured throught datastore: paramether.

  // config/datastores.js

  devMongoDb: {
    adapter: require('sails-mongo'),
    url: 'mongodb://user:pass@mongo:27017/devmongodb',
  },

// models/MongoModel.js

module.exports = {

  datastore: 'devMongoDb',

  attributes: {

    id: {
      type: 'string',
      columnName: '_id'
    },

    mymongoattribute: {
      type: 'string',
      required: true,
    },

  },

};

All working as expected. I can create models on both datastores without any problems using PostgresModel.create() and MongoModel.create().

But when i calling PostgresModel.archive() method on models that uses default datastore Archive collection appears in devMongoDb datastore.

It is posible to store Archive collection on the source datastore?

[sailsbot]

@TimurK Thanks for posting! We'll take a look as soon as possible.

In the mean time, there are a few ways you can help speed things along:

• look for a workaround. (Even if it's just temporary, sharing your solution can save someone else a lot of time and effort.)
• tell us why this issue is important to you and your team. What are you trying to accomplish? (Submissions with a little bit of human context tend to be easier to understand and faster to resolve.)
• make sure you've provided clear instructions on how to reproduce the bug from a clean install.
• double-check that you've provided all of the requested version and dependency information. (Some of this info might seem irrelevant at first, like which database adapter you're using, but we ask that you include it anyway. Oftentimes an issue is caused by a confluence of unexpected factors, and it can save everybody a ton of time to know all the details up front.)
• read the code of conduct.
• if appropriate, ask your business to sponsor your issue. (Open source is our passion, and our core maintainers volunteer many of their nights and weekends working on Sails. But you only get so many nights and weekends in life, and stuff gets done a lot faster when you can work on it during normal daylight hours.)
• let us know if you are using a 3rd party plugin; whether that's a database adapter, a non-standard view engine, or any other dependency maintained by someone other than our core team. (Besides the name of the 3rd party package, it helps to include the exact version you're using. If you're unsure, check out this list of all the core packages we maintain.)

  ---

Please remember: never post in a public forum if you believe you've found a genuine security vulnerability. Instead, disclose it responsibly.

For help with questions about Sails, click here.