Wow, Thanks for the quick reply. Here I was restructuring my SQL and everything and it was a simple name problem.
On May 24, 2:19 am, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Thu, 2007-05-24 at 06:10 +0000, Michael Newman wrote: > > This is appearing athttp://speakeasymag.com/staff/Mgnewman > > > I have been adjusting the SQL a bit but really don't understand why > > this error keeps appearing. I did a search and most people who had > > this problem were dealing with Utf-8 characters. This is an Id column > > from a foreignKey field, so it is an integer. > > > I really have no idea where to start on this one. Any help would be > > appreciated, > > For some reason, you're passing in a string (Mgnewman) where there > should be an integer. Unfortunately, the traceback nicely hides that > actual culprit function, which is your view, so we can't see what is the > root cause. But you need to investigate the line that is trying to do > the lookup. > > 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?hl=en -~----------~----~----~----~------~----~------~--~---
