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: > Hello, > > I am programming an application where a model instance could be > archived if necessary. For example: in gmail I can archive e-mails and > they move in the archived folder. > > The question is: is it only a boolean class-attribute called archived? > Or is there more technical know how behind it? > > If I have 20,000 entries in one model (table), a search takes longer > than with only 1,000 entries. Now is there a better solutions than > moving archived entries into another model (table)? … or a more common > solution? -- Thomas Guettler, http://www.thomas-guettler.de/ E-Mail: guettli (*) thomas-guettler + de --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
