On Oct 16, 11:02 am, Thomas Guettler <h...@tbz-pariv.de> wrote:
> Hi,
>
> If you use indices to access the models, you will see no noticable difference
> in speed between 1,000 and 100,000 rows. This may be different if use no
> indices (e.g. SQL LIKE "%...%"). But if the boolean column "archived" has
> an index, the sequential scan will be fast.
>
> I would *not* create a second table and "move" the data from one table
> to the other.
>
> Léon Dignòn wrote:
I agree with thomas, create Boolean attribute on your model and index
it
http://docs.djangoproject.com/en/dev/ref/models/fields/#db-index
It should be reasonably fast to say Model.objects.filter
(archive=False) even with a high row count.
You can even override admins change list queryset later to show only
records that have not been archived or you can set up a filter for it.
http://blog.dougalmatthews.com/2008/10/filter-the-django-modeladmin-set/
--~--~---------~--~----~------------~-------~--~----~
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
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
