Ron,
Understood, but Rose handles those sorts of things. And I use Postgres,
but other users of my code may not.
As I said in another reply, I'm fishing for ideas on how to display
these options in the web client, for the user's benefit.
I usually just give the user a preset list of options f
Hi Stephen
> Does your SQl support the LIMIT command? MySQL and PostgreSQL both do
> but with slightly different syntax. I think Oracle does too but SQL
> Server does not.
Understood, but Rose handles those sorts of things. And I use Postgres,
but other users of my code may not.
As I said in a
On Sun, May 25, 2008 at 6:37 PM, Ron Savage <[EMAIL PROTECTED]> wrote:
> Hi Folks
>
> Let's say I offered the user a form with 2 fields, id and (Winemaker's)
> name.
>
> The user enters B% for the name's value, and, using Rose, I know there
> are 18 matching records.
>
> But it happens I'm using a
Hi Cees
> If you are using Rose, then you don't need to bother with Data::Page.
> Rose provides convenience methods to do your limit/offset values.
Yes, I was wondering if I needed it at all.
> $products = Product::Manager->get_products(
> query =>
> [
> ...
> ],
>
On Mon, 2008-05-26 at 16:15 +1200, Dan Horne wrote:
> Ron Savage said:
> > The question is how to let the end user manage the
> > transition from page to page.
>
> Oh, I misunderstood. I guess in that case, why not use the pagination
> model used by Google with the page number at the footer of the
On Mon, May 26, 2008 at 1:36 PM, Ron Savage <[EMAIL PROTECTED]> wrote:
> Hi Dan
>
>> I like Data::Page::Navigation. Each link for selecting a page would
>> include the search criteria including the page number. DBIx::Class offers
>
> I'm intending to use Data::Page.
Hi Ron,
If you are using Rose,
Ron Savage said:
> The question is how to let the end user manage the
> transition from page to page.
Oh, I misunderstood. I guess in that case, why not use the pagination
model used by Google with the page number at the footer of the page
# CGI::Application community mailing list ###
Hi Dan
> I like Data::Page::Navigation. Each link for selecting a page would
> include the search criteria including the page number. DBIx::Class offers
I'm intending to use Data::Page.
> a database agnostic syntax for limiting the rows returned to the page
> requested, so I guess Rose would too
Ron Savage said:
> Hi Folks
>
> Let's say I offered the user a form with 2 fields, id and (Winemaker's)
> name.
>
> The user enters B% for the name's value, and, using Rose, I know there
> are 18 matching records.
>
> But it happens I'm using a per_page of 10 (say) to call
> get_winemaker_iterator(
Hi Folks
Let's say I offered the user a form with 2 fields, id and (Winemaker's)
name.
The user enters B% for the name's value, and, using Rose, I know there
are 18 matching records.
But it happens I'm using a per_page of 10 (say) to call
get_winemaker_iterator(), so the first call returns recor
10 matches
Mail list logo
