UUID primary key for MSSQL

[deksden]

After importing some MS SQL (2008R2) table i have following field definition in my model:

ID: {
     type: 'UNIQUEIDENTIFIER',
     allowNull: false,
     defaultValue: '(newid())',
     primaryKey: true
 }, 

Actually, IMHO, it should be like this:

ID: {
     type: DataTypes.UUIDV4,
     allowNull: false,
     primaryKey: true
 }, 

P.S. .UUIDV4 makes this field as uuid-type and auto-generate new value for it

[deksden]

Here is PR for this feature: #79

[leolorenzoluis]

@deksden Producing DataTypes.UUIDV4 breaks SQL Server. Getting an error that column data type UUIDv4 is not found. Changing the DataType to UUID fixes it. Could you double check?

[deksden]

Any code/sample? What SQL Server version?

As for time of that issue 2 yrs ago all was fine with tested SQL server versions

[alex-thompson]

For anyone else who stumbles across this today, you can keep UNIQUEIDENTIFIER (versus CHAR with DataTypes.UUID), by doing:

id: {
  type: 'UNIQUEIDENTIFIER',
  defaultValue: DataTypes.UUIDV4,
  primaryKey: true
},

Just keep the defaultValue as DataTypes.UUIDV4 versus the literal newid() to avoid breaking the model's associations.

[josuerodcat90]

For anyone else who stumbles across this today, you can keep UNIQUEIDENTIFIER (versus CHAR with DataTypes.UUID), by doing:

id: {
  type: 'UNIQUEIDENTIFIER',
  defaultValue: DataTypes.UUIDV4,
  primaryKey: true
},

Just keep the defaultValue as DataTypes.UUIDV4 versus the literal newid() to avoid breaking the model's associations.

Thanks a lot!!!, this still working if any else stuck with this.