> The World Online admin > interface (where Django was born) has a number of content types with > tens of thousands -- if not hundreds of thousands -- of records.
393,181 stories and counting... On 6/21/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > > On 6/21/06, Patrick Anderson <[EMAIL PROTECTED]> wrote: > > We have about 80,000 records which we will need to migrate. I'm wondering > > how Django admin interface would deal with such amount of data (they > > are of the same type, so they might be managed by a single app). I know > > Django comes from the news publishing world, where databases are huge, > > but this is a key question for us, and would like to hear comments that > > will put my concerns to rest, so we can start coding (well, we already > > have the models and the admin interface:)). Any tips would be appreciated, > > too. > > Hey Patrick, > > The admin interface really doesn't care about how many records you > have; the user interface is built to scale. I wouldn't expect to have > any problems with the admin interface. The World Online admin > interface (where Django was born) has a number of content types with > tens of thousands -- if not hundreds of thousands -- of records. > Pagination, filters and searches on the changelist are quite useful in > those cases! :) > > Generally when dealing with lots of records, the pressure point is the > database. Make sure your database is optimized for the data you have. > > Adrian > > -- > Adrian Holovaty > holovaty.com | djangoproject.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-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
