On Wed, Dec 9, 2009 at 11:18 AM, HUANG Dong <huangdong...@gmail.com> wrote:
> Thank you, Bruno. Your answer is really helpful and covered another > issue I hadn't noticed yet. But my question may be related to > different topic. In my example, number of "libraries" is unknown in > develop time, neither does the classification of "books". I suspect you could use a raw SQL command - "ADD PARTITION" - in MySQL to create a partition for each new library and/or classification. Then the database would take care of everything else (assuming that the library or classification is a column on which you define the partitioning), which would be a Good Thing (because this really doesn't belong at the application level if at all possible). Nick -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
