Home » Nodejs » Unique property fails in Sails.js

Unique property fails in Sails.js

Posted by: admin November 30, 2017 Leave a comment

Questions:

The following code represents an Account Model in Sails.js v0.9.4 .

 module.exports = {

      attributes: {
        email: {
          type: 'email',
          unique: true,
          required: true
        },
        password:{
          type: 'string',
          minLength: 6,
          maxLength: 15,
          required:true
        }
      }

    };

When I send two POSTS and a PUT request via Postman to localhost:8080/account, the unique property of the email fails.
Specifically, I send the following HTTP requests from Postman:

POST http://localhost:8080/[email protected]&password=123456  
POST http://localhost:8080/[email protected]&password=123456    
PUT  http://localhost:8080/account?id=1&[email protected]  
GET  http://localhost:8080/account

The last GET request shows me:

[
  {
    "email": "[email protected]",
    "password": "123456",
    "createdAt": "2013-09-30T18:33:00.415Z",
    "updatedAt": "2013-09-30T18:34:35.349Z",
    "id": 1
  },
  {
    "email": "[email protected]",
    "password": "123456",
    "createdAt": "2013-09-30T18:33:44.402Z",
    "updatedAt": "2013-09-30T18:33:44.402Z",
    "id": 2
  }
]

Should this happen?
*For those who don’t know, Waterline generates by default an id which automatically increments in every insertion.

Answers:

This is because your schema is not updated in your disk database (“.tmp/disk.db”).

You need to shutdown sails, drop your DB and restart sails.
The DB will be reconstruct with your good schema.

Attention : the data will be drop too !

If you want keep your data, you can just update the schema part of “.tmp/disk.db”.

What I have doing to keep data and rebuild schema by sails.js :

  1. copy “.tmp/disk.db”
  2. clean “.tmp/disk.db”
  3. shutdown sails.js
  4. start sails.js
    -> the database is empty and the schema is updated
  5. copy old “counters” part
  6. copy old “data” part

You must have this in your schema (file “.tmp/disk.db” -> “schema” part) for the unique field :

  "xxx": {
    "type": "string",
    "unique": true
  },

I hope this help you.

Questions:
Answers:

I ran into this same issue. To solve it, you have to avoid using the ‘disk’ ORM adapter. For some reason it appears that it doesn’t support uniqueness checks.

Other adapters such as mongo and mysql should support uniqueness checks, so this shouldn’t be an issue outside of development.

For the course of development, change the default adapter in config/adapters.js from ‘disk’ to ‘memory’. Should look like this:

module.exports.adapters = {

  // If you leave the adapter config unspecified 
  // in a model definition, 'default' will be used.
  'default': 'memory',

  // In-memory adapter for DEVELOPMENT ONLY
  memory: {
    module: 'sails-memory'
  },

  ...
};

Questions:
Answers:

I’m not certain this is the issue, but have you added schema:true to your models and adapters?

My mongo adapter config looks like this:

    module.exports.adapters = {
            'default': 'mongo',
            mongo: {
                    module: 'sails-mongo',
                    url: process.env.DB_URL,
                    schema: true
            }
    };

And my User model looks like this (trimmed a bit):

    module.exports = {
            schema: true,
            attributes: {
                    username: {
                            type: 'string',
                            required: true,
                            unique: true
                    }
                    //...
            }
    };

Questions:
Answers:
var InvoiceSchema = new Schema({
 email: {type: 'email', required: true}
  name : {type: String}
});
InvoiceScheme({email: 1}, {unique: true});

Set Uniquee In Nodejs

Questions:
Answers:

There is no need to delete current database to solve this, in stead change the waterline migrate option from safe to alter. This way the underlying database will adapt this setting.

I wouldn’t recommend migrate: alter in a production environment, though. 😉


Here is my /config/local.js:

module.exports = {

    ... 

    models: {
        migrate: 'alter'
    },
}

Questions:
Answers:

According to the official documentation of sails

You should configure the option “migrate” in “alter” to create the schemas with their indexes

There’s nothing wrong with adding or removing validations from your
models as your app evolves. But once you go to production, there is
one very important exception: unique. During development, when your
app is configured to use migrate: ‘alter’, you can add or remove
unique validations at will. However, if you are using migrate: safe
(e.g. with your production database), you will want to update
constraints/indices in your database, as well as migrate your data by
hand.

http://sailsjs.com/documentation/concepts/models-and-orm/validations