Re: pagination problem with "Next" and saving results as a dictionary

2009-03-16 Thread Jesse
Hello Paul, Thanks!! I'll try it. On Mar 13, 2:21 pm, pkenjora wrote: > Uhm maybe this post will help its a tag that handles thepaginationon > query objects.  I've used it in a few of my projects and > its quite handy. > > http://blog.awarelabs.com/?p=29 > > -Paul > > On Mar 13, 12:13 pm,

Re: pagination problem with "Next" and saving results as a dictionary

2009-03-13 Thread pkenjora
Uhm maybe this post will help its a tag that handles the pagination on query objects. I've used it in a few of my projects and its quite handy. http://blog.awarelabs.com/?p=29 -Paul On Mar 13, 12:13 pm, Jesse wrote: > Hello Micah, > > I can get the q with GET, but I have too complicated o

Re: pagination problem with "Next" and saving results as a dictionary

2009-03-13 Thread Jesse
Hello Micah, I can get the q with GET, but I have too complicated of a search and I need to use POST. I'm having much difficulty with my template code with POST to work with paginator. I'll keep trying. Thanks for your patience and help. --~--~-~--~~~---~--~~

Re: pagination problem with "Next" and saving results as a dictionary

2009-03-12 Thread Micah Ransdell
Jesse, You need to change your code in the view to look at the GET parameter rather than POST. Change this line: query = request.POST['q'] to: query = request.GET['q'] Also, make sure when you are submitting to your search page that you are submitting the page with GET in the method of your fo

Re: pagination problem with "Next" and saving results as a dictionary

2009-03-12 Thread Jesse
Hello Micah, I tried this in the template: next The browser URL is: http://127.0.0.1:8000/Search/?q=?&page=2 and this in the template: next The browser URL is: http://127.0.0.1:8000/Search/?q=harris&page=2, which is correct for q, but the error for both is still: Request Method: GE

Re: pagination problem with "Next" and saving results as a dictionary

2009-03-12 Thread Jesse
Hello Micah, My view is too commplicated. The q and the pathologyid ( I actually have two other retrievals that also appended with these) are all appended into the "list". What I need to figure out is how to send the "list" to it's own dictionary, which I can then retrieve with a new view and u

Re: pagination problem with "Next" and saving results as a dictionary

2009-03-11 Thread Micah Ransdell
Jesse, The error you are getting is from "q" not being in your post QueryDictionary. This happens because when you click next you are not rePOSTing the q variable. Either you can put the q variable into an input box and POST it again by making your next link a submit button, or you could change q

pagination problem with "Next" and saving results as a dictionary

2009-03-11 Thread Jesse
The following code is for a search on q and attaches tuples from the search on another model. The search results are appended together to create the final data results "list". def Bypub(request): query = request.POST['q'] if query: qset = ( Q(pubtitlestrip__icontains=q