> 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.
No, it fails for me, we are on the same page. > 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. Latest MacOSX, python 2.4, latest Django .96? I suspect then that I have a model that is more complex /different from the database. In other posts I have mentioned the problems associated with evolving apps.. I have tried to make sure that I do the appropriate ALTER statements when updating my model but obviously cocked something up... Is there a way to do a complete dump, re-build the database and then import stuff (avoiding import errors... i.e doing some form of coercion)? > 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? Latest MacOSX, python 2.4.3, latest Django .96? Mysql 5.0.19 (the one that comes with MAMP) Thanks for your help and time... not sure how I need to move forward on this one... regards tom --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
