The table is queried from ajax using an autocomplete field with this query in the views.py:
books.objects.filter(book_title__istartswith=request.GET['q'])[:100] --------------- On Jan 12, 8:47 pm, Chris Czub <[email protected]> wrote: > It really depends on how you're selecting the data from the database. If > you're doing something that necessitates a full table scan(like in-DB ORDER > BY) it will slow you down considerably. If you're selecting one row from the > database by an indexed column, then the performance will be very fast and > there's no need to prematurely optimize. > > On Tue, Jan 12, 2010 at 2:25 PM, nameless <[email protected]> wrote: > > My table with 4 milions of rows is queried often by ajax. > > So I think a performance problems ( I am using also index ). > > Ok now take a look at the contenttypes :) > > > ------------ > > > On Jan 12, 8:15 pm, Tim <[email protected]> wrote: > > > As far as needing to split up the table into other tables, I'm not > > > sure. Whats wrong with having 4 million records in one table? > > > > But if you're going to do it, take a look at the contenttypes > > > framework and generic relations. It basically does what you're > > > describing: > > > >http://docs.djangoproject.com/en/dev/ref/contrib/contenttypes/#id1 > > > -- > > You received this message because you are subscribed to the Google Groups > > "Django users" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<django-users%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/django-users?hl=en. > >
-- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
