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.
