Trev wrote: > Am I thinking about this wrong performance wise? all SQL engines i know about either ignore the REFERENCES hint, or use it for defining constraints. the SQL "...WHERE t1.fk=t2.pk" clause is enough to optimally use any index that could help. when Django creates the tables, it makes sure to add any index that would help on the usual JOINs
-- Javier -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=.
