Also a dumb question. Did you syncdb after you created your models?
The table may not actually exist yet. You might have to create it by
hand of you have already created the model and validated then synced.
Make sense?
On May 20, 12:30 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Sun, 2007-05-20 at 19:22 +0000, Roboto wrote:
> > This is what I'm currently runnign with now...
>
> > user_list = Access.objects.filter(team =
> > team_profile).exclude(status = "NON")
> > roster = user_list.extra(
> > select={
> > 'first_name': 'SELECT first_name FROM Personal
> > WHERE user = user_list.user'
> > }
> > )
>
> > Although I get the following error return to me:
> > ProgrammingError: ERROR: relation "personal" does not exist
>
> One hesitates to ask the obvious question, but does a table by that name
> exist? It's quite likely the error message is telling you exactly what
> the problem is. Django's database tables are typically of the form
> app_model, not a single word.
>
> 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 [email protected]
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
-~----------~----~----~----~------~----~------~--~---
