On Wed, 2006-10-11 at 19:53 +0100, Tom Smith wrote:
> 
> On 11 Oct 2006, at 18:59, Rajesh Dhawan wrote:
[...]
> > 
> > Perhaps try upgrading to a recent SVN of Django? I am on 0.96-pre.
> > 
> 
> 
> I upgraded...
> 
> 
> 
> > Also, I am using SQLite for the DB but that should not matter, I
> > think.
> > 
> 
> 
> I'm using MySQL...  It would seem that is where the problem will
> lie... this is a bug I reckon
> 

No, because when I tested the example you posted yesterday, I tested it
against MySQL as well. No problems there. Plus the error message you are
seeing is generated by Django before it attempts to talk to the
database.

Just to establish that we are all on the same page: are you seeing the
error when you use exactly the model example you posted yesterday and
cut and paste the queryset constructor that Rajesh posted? That should
be working.

If that is failing for you, there is something odd about your setup that
we need to debug. If you are trying to run these examples against a
different model (e.g. the more complex one you started with), then you
are introducing extra variables into the problem and that isn't helping
at all.

Other information that might help if the problem persists: which Python
version are your using? What platform (Mac OS, Linux, Windows, Solaris,
VMS, AIX, lemon-powered-OS, ...)? What version of Django?

Regards,
Malcolm



--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to