| From: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
|---|---|
| To: | Allan Kamau <kamauallan(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Implementing next 30 (or so) rows "sliding window" |
| Date: | 2009-12-08 19:42:50 |
| Message-ID: | 3073cc9b0912081142x4738ed1of5bd457edb19787b@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Dec 8, 2009 at 2:12 PM, Allan Kamau <kamauallan(at)gmail(dot)com> wrote:
> Hi,
> I did follow the basic advise and consulted the documentation for
> "SELECT" and came across "[ FETCH { FIRST | NEXT } [ count ] { ROW |
> ROWS } ONLY]" clause which seems to satisfy my requirement.
>
that's basically LIMIT, you have to combine that with OFFSET
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Lelarge | 2009-12-08 20:11:11 | Re: Tuesday (PST8PDT) Jeff Davis Presents: Operator Exclusion Constraints |
| Previous Message | Allan Kamau | 2009-12-08 19:12:26 | Re: Implementing next 30 (or so) rows "sliding window" |