Primary key should be same as unique key (doc change) (#6251)

* Primary key should be same as unique key If not, a primary key for taggable_id is created, so no more than one tag per taggable could be created. * Define id If not, a primary key for taggable_id is created, so no more than one tag per taggable could be created.

Primary key should be same as unique key (doc change) (#6251)
* Primary key should be same as unique key If not, a primary key for taggable_id is created, so no more than one tag per taggable could be created. * Define id If not, a primary key for taggable_id is created, so no more than one tag per taggable could be created.
ivesdebruycker · Mick Hansen
Commit 8a4f5280 authored Jul 11, 2016 by ivesdebruycker Committed by Mick Hansen Jul 11, 2016
Showing with 5 additions and 0 deletions
docs/docs/associations.md
--- a/docs/docs/associations.md
+++ b/docs/docs/associations.md
@@ -342,6 +342,11 @@ For brevity, the example only shows a Post model, but in reality Tag would be re

 ```js
 ItemTag = sequelize.define('item_tag', {
+  id : {
+    type: DataTypes.INTEGER,
+    primaryKey: true,
+    autoIncrement: true
+  },
  tag_id: {
    type: DataTypes.INTEGER,
    unique: 'item_tag_taggable'