Re: [Django] #11866: non-null FK to a CharField primary key fails when key value is the empty string, giving "[model.fk_col] may not be NULL"

[Django]

#11866: non-null FK to a CharField primary key fails when key value is the empty
string, giving "[model.fk_col] may not be NULL"
-------------------------------------+-------------------------------------
Reporter: andrewbadr | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.1
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by akaariai):

* stage: Design decision needed => Accepted

Comment:

This should be fixed at some point. The fix should involve making sure ''
works as expected in other parts of Django, too.

--
Ticket URL: <https://code.djangoproject.com/ticket/11866#comment:8>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#11866: non-null FK to a CharField primary key fails when key value is the empty
string, giving "[model.fk_col] may not be NULL"
-------------------------------------+-------------------------------------
Reporter: andrewbadr | Owner: nobody

Type: Bug | Status: closed

Component: Database layer | Version: 1.1
(models, ORM) |

Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):

* status: new => closed
* resolution: => duplicate

Comment:

Duplicate of #19299; fixed in Django 1.7.

--
Ticket URL: <https://code.djangoproject.com/ticket/11866#comment:9>