One related question on nullable foreign keys: does the Django ORM always use inner/left joins for select_related() calls? If so, null FKs will cause rows to be excluded from a query so you may have to handle these with direct SQL.
Personally, I often create an "unknown" row in a table (and do a little trickery to set its auto-increment ID to 0) and use this special value for the same cases you might use a null ID for. It ensures all your queries are simple and always return complete result sets, but still allows you to easily query for (or exclude) these special cases. -Dave --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
