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".
To be more specific, I want to employ some kind of "introspective"
class in python to model my data, and these dynamic classes should be
associated to individual TABLEs in the database respectively. Surely
writing my own modeling middleware is an approach. However, I am not
sure whether Django's model has such a feature already. If so, I need
not to reinvent the wheel.
So far what I know about Django is that each class inheriting from
models.Model will be associated to a TABLE, and each instance of the
class becomes an item when calling instance.save(). What if I create
an introspective object in run-time? And when to call synchronization
function to write the table into database? How to sync if there's
concurrent creation of classes? What about the performance? All
above are still unknown to me...
Thanks,
Huang
On Thu, Dec 10, 2009 at 12:42 AM, bruno desthuilliers
<bruno.desthuilli...@gmail.com> wrote:
> On 9 déc, 17:26, Huang Dong <huangdong...@gmail.com> wrote:
>> Suppose I have a class "Book". Typically Django will create a table
>> in database for the class. If there are millions or even billions of
>> books, I don't want to place them into one large table. Instead, I
>> want to group them into different tables ("libraries"), in order to
>> speed up querying given the user explicitly knows which library to
>> query. But I don't know how to do so after browsing the Django
>> documentation. Could anybody help me?
>
> This is named "horizontal partitioning", and is probably better solved
> at the RDBMS level when possible - decoupling data access (logical
> level) from data storage (physical level) so your application is not
> impacted being one of the goals of a RDBMS...
>
> Good news is that PGSql and MySQL do support partitionning:
>
> http://www.postgresql.org/docs/8.1/interactive/ddl-partitioning.html
> http://dev.mysql.com/tech-resources/articles/performance-partitioning.html
>
> HTH
>
> --
>
> 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.
>
>
>
--
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.
