Changed create() and get_or_create() to force an insert (not update an existing value).
commitc5be955017eef56cb7476c60a6dab3f56068bf53
authormtredinnick <mtredinnick@bcc190cf-cafb-0310-a4f2-bffc1f526a37>
Thu, 28 Aug 2008 17:18:05 +0000 (28 17:18 +0000)
committermtredinnick <mtredinnick@bcc190cf-cafb-0310-a4f2-bffc1f526a37>
Thu, 28 Aug 2008 17:18:05 +0000 (28 17:18 +0000)
tree2a3f64688e59d666684dfa93da1a52642f186d0d
parentc56d617b232b82f81c704d64a008127da6c56409
Changed create() and get_or_create() to force an insert (not update an existing value).

Backwards incompatible if you are using manually-specific primary key values
and relying on the previously documented behaviour that the new values would
always exist in the database (i.e. it would update the existing entry).

Fixed #8419.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@8670 bcc190cf-cafb-0310-a4f2-bffc1f526a37
django/db/models/query.py
docs/ref/models/instances.txt
docs/ref/models/querysets.txt