Re: Some more curious performance issues between MySQL and Django ORM

2011-07-14 Thread Cal Leeming [Simplicity Media Ltd]
On Thu, Jul 14, 2011 at 2:17 PM, bruno desthuilliers < bruno.desthuilli...@gmail.com> wrote: > On 14 juil, 02:24, "Cal Leeming [Simplicity Media Ltd]" > wrote: > > On 14 Jul 2011 00:13, "bruno desthuilliers" < > bruno.desthuilli...@gmail.com> > > wrote: > >> And FWIW, did you try the obvious: > >

Re: Some more curious performance issues between MySQL and Django ORM

2011-07-14 Thread bruno desthuilliers
On 14 juil, 02:24, "Cal Leeming [Simplicity Media Ltd]" wrote: > On 14 Jul 2011 00:13, "bruno desthuilliers" > wrote: >> And FWIW, did you try the obvious: > >> return Session.objects.filter( >>            member__username=self.username, >>            is_fake = 0 >>         ).order_by("-id") > >

Re: Some more curious performance issues between MySQL and Django ORM

2011-07-14 Thread Cal Leeming [Simplicity Media Ltd]
On 14 Jul 2011 03:11, "Andre Terra" wrote: > > PostgreSQL or bust. Hehe, a lot of people have suggested using PostgreSQL, and in all fairness I do now understand some of the arguments in the MySQL vs debate.. Until i find something really really wrong with mysql, ill probably 'stay with the devil

Re: Some more curious performance issues between MySQL and Django ORM

2011-07-13 Thread Andre Terra
PostgreSQL or bust. On Wed, Jul 13, 2011 at 9:24 PM, Cal Leeming [Simplicity Media Ltd] < cal.leem...@simplicitymedialtd.co.uk> wrote: > > On 14 Jul 2011 00:13, "bruno desthuilliers" > wrote: > > > > On 13 juil, 21:37, "Cal Leeming [Simplicity Media Ltd]" > > wrote: > > > > > _users =

Re: Some more curious performance issues between MySQL and Django ORM

2011-07-13 Thread Cal Leeming [Simplicity Media Ltd]
On 14 Jul 2011 00:13, "bruno desthuilliers" wrote: > > On 13 juil, 21:37, "Cal Leeming [Simplicity Media Ltd]" > wrote: > > > _users = map(lambda x: x.get('memberid'), Members.objects.filter( > > username = self.username > > ).values('memberid')) > > What's wrong with

Re: Some more curious performance issues between MySQL and Django ORM

2011-07-13 Thread bruno desthuilliers
On 13 juil, 21:37, "Cal Leeming [Simplicity Media Ltd]" wrote: >         _users = map(lambda x: x.get('memberid'), Members.objects.filter( >             username = self.username >         ).values('memberid')) What's wrong with values_list ? member_ids = Members.objects.filter(

Re: Some more curious performance issues between MySQL and Django ORM

2011-07-13 Thread Cal Leeming [Simplicity Media Ltd]
Sorry, let me rephrase to avoid confusion. The original query I showed took about 4 seconds in total. The modified query underneath took around 0.2s in total. Cal On Wed, Jul 13, 2011 at 11:08 PM, Cal Leeming [Simplicity Media Ltd] < cal.leem...@simplicitymedialtd.co.uk> wrote: > The first que

Re: Some more curious performance issues between MySQL and Django ORM

2011-07-13 Thread Cal Leeming [Simplicity Media Ltd]
The first query took around 4 seconds, the latter took around 0.2s. :) On 13 Jul 2011 21:15, "Andre Terra" wrote: > On Wed, Jul 13, 2011 at 4:37 PM, Cal Leeming [Simplicity Media Ltd] < > cal.leem...@simplicitymedialtd.co.uk> wrote: > > (...) > > >> ** >> *This original query took 4 seconds to com

Re: Some more curious performance issues between MySQL and Django ORM

2011-07-13 Thread Andre Terra
On Wed, Jul 13, 2011 at 4:37 PM, Cal Leeming [Simplicity Media Ltd] < cal.leem...@simplicitymedialtd.co.uk> wrote: (...) > ** > *This original query took 4 seconds to complete:* > > # return sessions for all subscriptions under this username > _users = Members.objects.filter( >

Some more curious performance issues between MySQL and Django ORM

2011-07-13 Thread Cal Leeming [Simplicity Media Ltd]
Most of you will probably read this and say "duh", so this is aimed more at people who haven't had experience with using large data sets in Django. This isn't necessarily a bug or a problem with the ORM (although it would be nice if it could try and utilize little gotcha's like this), it just show

Re: mysql and Django

2010-10-18 Thread emma
Thanks a lot! I have installed the new mysql-python under my home directory and change PYTHONPATH. Now Django works well. Cheers. On Oct 16, 1:01 am, David wrote: > I think there is some confusion here. I'm guessing you are using mysql- > python v1.2.1 since a 1.x mysql version would probably d

Re: mysql and Django

2010-10-15 Thread David
I think there is some confusion here. I'm guessing you are using mysql- python v1.2.1 since a 1.x mysql version would probably date back to the mid to late 90s. Ask the admin if it is possible to upgrade mysql- python for which you do not need to upgrade MySQL itself or even take down the database.

mysql and Django

2010-10-15 Thread emma
Hi, the linux server of my company has mysql 1.2.1, which is too old for Django. However, the administrator didn't want to upgrade it. I have to install mysql 5.1.51 under my home directory. I did that successfully, but Django still complain about the older mysql. Do you know if there is a way to c

Re: id problem with mysql and django models

2008-08-30 Thread eniac
Thanks for the advice ! Everhting seems to work fine now. Only when I enter s.id it return nothing and when I print s.id it returns None. Guess that's normal since the s-object hasn't been saved yet ? On Aug 30, 7:13 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Sat, 2008-08-30 at 06:56

Re: id problem with mysql and django models

2008-08-30 Thread Malcolm Tredinnick
On Sat, 2008-08-30 at 06:56 -0700, eniac wrote: > Hello, > > I'm using django 0.96.1 on ubuntu. > I'm going to describe the steps I went through until I encountered > something odd. > > I create a model: > > class shoutbox(models.Model): > name = models.CharField(maxlength=15) >

id problem with mysql and django models

2008-08-30 Thread eniac
Hello, I'm using django 0.96.1 on ubuntu. I'm going to describe the steps I went through until I encountered something odd. I create a model: class shoutbox(models.Model): name = models.CharField(maxlength=15) shout = models.CharField(maxlength=256) pub_date = models.Dat