Thanks Javier.
It seems that I was perhaps thinking about it the wrong way. I
believe I understand what you mean - the REFERENCE just keeps the
table in order, it doesn't provide any performance boost. The speed
boost comes from the indexes that are created, which Django
automatically sets up.
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
ma
Hi there,
I am new to Django and SQL, and I'm putting together my first Django
project. My project will contain multiple apps, and one app has a
model that I'd like to "One To One" extend with a table in a different
app. However, it's not behaving how I'd expect, and I can't seem to
find any inf
3 matches
Mail list logo
