Re: executing raw sql results in traceback

2009-02-12 Thread Bobby Roberts
On Feb 12, 3:29 pm, Karen Tracey wrote: > On Thu, Feb 12, 2009 at 10:26 AM, Bobby Roberts wrote: > > > My apologies... I didn't see Alex's post.  Google some times collapses > > threads on me.  Replacing % with %% seemed to work.  It queries the > > database and returns a dataset like this: >

Re: executing raw sql results in traceback

2009-02-12 Thread Karen Tracey
On Thu, Feb 12, 2009 at 10:26 AM, Bobby Roberts wrote: > > My apologies... I didn't see Alex's post. Google some times collapses > threads on me. Replacing % with %% seemed to work. It queries the > database and returns a dataset like this: > > ((6L, u'WI', u'ST', u'test3', u'test3', u'test3',

Re: executing raw sql results in traceback

2009-02-12 Thread Bobby Roberts
> but I'm not entirely sure of that since you still haven't provided the > actual traceback which would show what code, exactly, is running into > trouble.  Without the traceback I have to fall back on my crystal ball, and > it's pretty cloudy at the moment. > > Karen My apologies... I didn't se

Re: executing raw sql results in traceback

2009-02-12 Thread Karen Tracey
On Thu, Feb 12, 2009 at 8:11 AM, Bobby Roberts wrote: > > On Feb 11, 8:38 pm, Bobby Roberts wrote: > > On Feb 11, 8:01 am,BobbyRoberts wrote: > > > > > there shouldn't be really. The client has a search form and due to > > > the way they want the search done there are about 40 option checkboxes

Re: executing raw sql results in traceback

2009-02-12 Thread Bobby Roberts
On Feb 11, 8:38 pm, Bobby Roberts wrote: > On Feb 11, 8:01 am,BobbyRoberts wrote: > > > there shouldn't be really.  The client has a search form and due to > > the way they want the search done there are about 40 option checkboxes > > for filtering in about 5 categories.  It would have been easie

Re: executing raw sql results in traceback

2009-02-11 Thread Bobby Roberts
On Feb 11, 8:01 am, Bobby Roberts wrote: > there shouldn't be really.  The client has a search form and due to > the way they want the search done there are about 40 option checkboxes > for filtering in about 5 categories.  It would have been easier if a > filter with IN could have been used but

Re: executing raw sql results in traceback

2009-02-11 Thread Alex Gaynor
On Wed, Feb 11, 2009 at 8:01 AM, Bobby Roberts wrote: > > there shouldn't be really. The client has a search form and due to > the way they want the search done there are about 40 option checkboxes > for filtering in about 5 categories. It would have been easier if a > filter with IN could have

Re: executing raw sql results in traceback

2009-02-11 Thread Bobby Roberts
there shouldn't be really. The client has a search form and due to the way they want the search done there are about 40 option checkboxes for filtering in about 5 categories. It would have been easier if a filter with IN could have been used but the way the search logic is setup that is not an o

Re: executing raw sql results in traceback

2009-02-10 Thread Karen Tracey
On Tue, Feb 10, 2009 at 10:28 PM, Bobby Roberts wrote: > > hi gang. For various reasons i've decided to use a raw sql statement > in my view. Following the example located at > http://docs.djangoproject.com/en/dev/topics/db/sql/, I have a view > which looks like this: > > > def searchform(reque

executing raw sql results in traceback

2009-02-10 Thread Bobby Roberts
hi gang. For various reasons i've decided to use a raw sql statement in my view. Following the example located at http://docs.djangoproject.com/en/dev/topics/db/sql/, I have a view which looks like this: def searchform(request): from django.db import connection ... # a massive sql statem