Karen,

You were spot on it was an error in the models file, thank you so so
much!
Very much appreciated.

On Jul 5, 5:45 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote:
> On Sat, Jul 5, 2008 at 3:03 AM, Arif <[EMAIL PROTECTED]> wrote:
> > Thanks for your reply but I don't think it is a problem with the
> > models, the same scripts work on my old Windows machine on localhost,
> > and the scripts work on my production linux server.
>
> > I have only had this problem since I installed Django on my new
> > Macbook Pro, sorry I should have mentioned that.
>
> You may not think your models file is the problem, but the fact that your
> model code is present in the traceback:
>
>   File
>
> > "/Library/Python/2.5/site-packages/django/core/management/validation.py",
> > line 60, in get_validation_errors
> >    for c in f.choices:
> >  File "/Users/Arif/Sites/Acquisition
> > App/acquisitionapp/../acquisitionapp/app/models.py", line 184, in __iter__
> >    for o in Organisation.objects.filter(models.Q(administrator=user) |
> > models.Q(participants=user)).distinct():
>
> points to your models file being a trigger for the problem.  Thus sharing it
> with us would make it easier to help you.  The error is that when this line
> of code is executed, the Organisation table does not exist in the database.
> It is possible you did not see this error on your Windows development/Linux
> production machines because you first created a models.py file that included
> the Organisation, ran syncdb on that, which created the Organisation table,
> and only later added the code that relies on the table existing.  Now you
> are starting afresh on a new machine you run into trouble because on the new
> machine's database the table doesn't yet exist.  But I'm just guessing based
> on the limited information you've provided.
>
> I do not think the error has anything to do with Macbook Pro vs. Windows or
> Linux.  There are plenty of people running on Macs and I can't recall any
> similar problems posted in relation to Macs.  Which, again, argues for it
> being something in your code that is causing the error.
>
> Karen
--~--~---------~--~----~------------~-------~--~----~
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?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to