Re: How would Django handle a large number of records

On 6/21/06, Patrick J. Anderson <[EMAIL PROTECTED]> wrote: > There are a few small admin interface issues I'd still need to work > out, mainly I might have a similar number of records related to > articles (the number of article assignments might be slighltly smaller > to the number of articles, l

Re: How would Django handle a large number of records

Thanks, guys! That's what I thought, but it helps to have a conformation, Wilson:). Great job on Django! There are a few small admin interface issues I'd still need to work out, mainly I might have a similar number of records related to articles (the number of article assignments might be slighlt

Re: How would Django handle a large number of records

> 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 PROTE

Re: How would Django handle a large number of records

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 t

How would Django handle a large number of records

Hi! I'm impressed with Django and all the fuss that it removed from my development. Our organisation is considering moving our document management from an old Access db to PostgreSQL and I thought of using django as an admin interface, plus public interface (sometime down the line.) We have abou