Yes, I specified db_table in Meta because I created the database
beforehand. I believe the problem was caused by using
ManyToManyFields. I switched it to ForeignKey fields and now I don't
receive the error. But maybe I should ask you a question about which I
should be using:
(Table1)---<Relation>---(Table2)
Normally that relation would be stored in its own table, a table with
two columns - Table1.ID and Table2.ID. From what I read in the Django
API doc, defining this in models.py does not involve writing a
separate class for that relation table. How is this then done?
On Feb 7, 8:24 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote:
> On Feb 7, 2008 7:48 PM, SeanFromIT <[EMAIL PROTECTED]> wrote:
>
>
>
> > I'm trying a very simple filter.
>
> > views.py:
> > from django.shortcuts import render_to_response
> > from project.app.models import Table_Name
> > def browse(request, Field_Name):
> > result = Table_Name.objects.filter(Field_Name=Field_Name)
> > return render_to_response('template/file.html', {'result':
> > result})
>
> > I get a ProgrammingError, table does not exist, because it tries to
> > dynamically change "Table_Name" to "Table_Name_Field_Name". Why is it
> > doing this?
>
> What's the definition for Table_Name? You don't by any chance have a
> table_name specified under Meta for it, do you?
>
> 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
-~----------~----~----~----~------~----~------~--~---
