Re: Several Custom SQL Pagination 1.2

OK it wasn't that simple but it worked.
I managed to move transfer the query terms and the query types into
the model this way.
its not a pretty sight but it does the job.

I have one problem but its a thing for another thread

On Oct 29, 12:54 am, Ita <zip...@gmail.com> wrote:
> Now that I think about it maybe its not that difficult.
> The paginate function has a scope parameter which can be used to pass
> sql condition.
> I could try and pass some kind of hint in this array about the search
> I want to preform.
> hmmmmmmmmmmmm.....
> Should work.
>
> Too late to check it now but will do it tomorrow and write about it
> afterwards.
>
> On Oct 29, 12:34 am, Ita <zip...@gmail.com> wrote:
>
> > Hello,
> > I have just implemented pagination successfully but seem to have a
> > problem with expanding this.
> > Iĺl explain.
>
> > I have a controller that can do several kind of searches.
> > lets say it has the following functions:
> > searchByAAA
> > searchByBBB
> > searchByCCC
> > searchByDDD
>
> > each search is complicated and has to be done using custom SQL query.
> > Now when I implement pagination I need to pass this SQL to the
> > paginator which I undestand cannot be done.
> > I know I can override the model paginate and paginateCount functions
> > but this will only help me in one case.
> > How do I know which SQL to run?
> > Can I pass some kind of parameter to the paginate function so Iĺl know
> > from where I´m coming?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to cake-php+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---