Lance,
I wouldn't worry too much about having empty fields vs an extra table
in your database. I think having data models that are easy to work
with is far more important than making sure you don't have fields that
are empty some time. I wouldn't worry at all about a field that is
empty a lot. I w
On the many to many field,
Great info, I'll look into those.
On combining the fields,
'Thumbs' is really Thumbnail images of 'Images'.
However, not all 'Images' have 'Thumbs'
Thinking that 3 possibly blank fields in 'Images' is more efficient
than 9 fields in a different table for each actual
Lance,
Regarding the many to many field that shows too many images:
I've used this project with some success in the past:
http://code.google.com/p/django-ajax-filtered-fields/
They allow you to setup some ajax filtering for the field, which can
make it a lot easier to find what you are looking fo
Ok, I'm just getting back to a project I had to put on hold for a
while.
I recently read an article on problems new Django users fall into, and
I think I hit one.
The bottom of my 'Systems' model looks like this:
keyboard = models.CharField(max_length=80)
cart = models.CharField(
4 matches
Mail list logo
