I have this model:
class Photo(Model):
title = CharField(
maxlength = 80,
)
description = TextField()
photo = ImageField(
upload_to = "photos/%Y/%m/%d",
height_field = "H",
width_field = "W",
)
W = PositiveSmallIntegerField("Width", null=True, editable=False)
H = PositiveSmallIntegerField("Height", null=True, editable=False)
W and H are both set to null=True, because I found that if you used
the default of null=False, and created the columns as NOT NULL, you'd
get a database error upon the initial add because the columns were
being set to NULL. However, if you set them to null=True so that they
can contain NULL, they *do* get the dimensions saved to them. There
seems to be an intermediate step where the row is first inserted with
NULLs for those fields and then it is updated. The workaround is to
null=True and editable=False so that the user can't futz with these
values, but it would be better if null=False worked.
The docs (trunk) currently say about ImageField's height_field and
width_field that the referenced fields are auto-populated "each time a
model instance is saved" but that seems to not be literally true.
If this seems bug-worthy, let me know.
--
Patriotism means to stand by the country. It does
not mean to stand by the president. -- T. Roosevelt
This message has been scanned for memes and
dangerous content by MindScanner, and is
believed to be unclean.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
