I'm a little late, but if you create the correct indexes on the table,
you will be fine.
Also, use unique id fields as much as possible for linking your tables.
Carl
nameless wrote:
Hi at all. I have a project with 2 applications ( books and reader ).
Books application has a table with 4 milions of rows with this fields:
book_title = models.CharField(max_length=40)
book_description = models.CharField(max_length=400)
To avoid to query the database with 4 milions of rows, I am thinking
to divide it by subject ( 20 applications with 20 tables with 200.000
rows ( book_horror, book_drammatic, ecc ).
In "reader" application, I am thinking to insert this fields:
reader_name = models.CharField(max_length=20, blank=True)
book_subject = models.IntegerField()
book_id = models.IntegerField()
So instead of ForeignKey, I am thinking to use a integer
"book_subject" (which allows to access the appropriate table) and
"book_id" (which allows to access the table specified in the book
"book_subject").
Is a good solution to avoid to query a table with 4 milions of rows ?
Is there an alternative solution ?
Thanks ^__^
--
Carl Zmola
301-562-1900 x315
czm...@woti.com
--
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=en.
