nkeric wrote:
>Really? That's cool!
>
>
Yes. One of the great new features of m-r branch is that relation
queries work similary for M-M and 1-M relations and in both directions:
game.articles.filter(article_type__pk=1) # all articles for one game
of one type
article.game_set.all() # all games from one article
and even
article.game_set.filter(article__article_type__pk=1)
... which gives all games mentioned in the article that was mentioned in
other articles of certain type (though it's not very practicle :-) )
>Our site (http://www.ifaxian.com - a Chinese Digg-like site) built upon
>the svn trunk version, we're planning to migrate to the m-r branch
>soon, I guess it's time for me to take a deeper look into the m-r
>branch :)
>
>
My advice is to making it sooner than later. I just killed the whole day
yesterday refactoring my project (medium sized mp3 exchange service with
wishlists, catalog, search and a blog) to magic removal. The most time I
spent converting old SQL queries to new ORM calls. So the more old stuff
you have the more you will have to convert.
If you fancy an example... To track downloads I have a DownloadLog table
that basically just references Users and Albums with foreign keys. There
was one query that selects "albums downloaded by users that have
downloaded this album". In trunk version there was an SQL of two nested
selects that looked pretty scary. Now it's just one line:
Album.objects.filter(downloadlog__user__downloadlog__album__pk=self.id).exclude(pk=self.id).distinct()
... which almost can be read in English ("albums in logs with users in
logs with this album").
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
