#2993 closed defect (fixed)
changeset 3960 broke Datefields and LazyDate()
Reported by: | Owned by: | Russell Keith-Magee | |
---|---|---|---|
Component: | Database layer (models, ORM) | Version: | |
Severity: | normal | Keywords: | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
A reminder ticket, see this thread for details:
http://groups.google.com/group/django-developers/browse_frm/thread/9895b1ef91d8411b
Attachments (1)
Change History (5)
comment:1 by , 18 years ago
Owner: | changed from | to
---|
comment:2 by , 18 years ago
I attached a quick fix that at least got LazyDate()
working again. The crux is that LazyDate
is not a datetime.* instance - it is a plain object, proxying __getattr__
to datetime. So the introduced isinstance()
tests do not apply. The patch switches back to the old is not None
test.
For reference, the error message I got was the good old mate can't adapt
from PostgreSQL. I love that message ;)
by , 18 years ago
Attachment: | lazydate-no-isinstance.diff added |
---|
comment:3 by , 18 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:4 by , 18 years ago
I forgot to annotate the fact that the last comment refers to changeset [4105]
Sorry - didn't get a chance to work on this bug when I said I would. RSN, I promise :-)