| From: | Patrick Baker <patrickbakerbr(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PL/PGSQL + inserts+updates+limit - Postgres 9.3 |
| Date: | 2016-06-03 03:59:43 |
| Message-ID: | CAJNY3itsKTbAZm=NbVmfN5tgzWDF-=7tPdYOtR29Ap9mZfOsYg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
2016-06-03 15:50 GMT+12:00 David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>:
> On Thu, Jun 2, 2016 at 11:37 PM, Patrick Baker <patrickbakerbr(at)gmail(dot)com>
> wrote:
>
>>
>> How can I make the function to gets the next 3 rows and not use the same
>> rows that have been used before?
>>
> WHERE migrated = 0
>
> David J.
>
>
>
lol... that's right David J. Thanks for that! it's working... ;)
Last thing.. how to select the number of rows that have been modified?
I mean.. when doing: select function_data_1():
I want to get back the number of rows that have been touched..
do u know how ?
thanks again
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2016-06-03 04:31:00 | Re: PL/PGSQL + inserts+updates+limit - Postgres 9.3 |
| Previous Message | David G. Johnston | 2016-06-03 03:50:33 | Re: PL/PGSQL + inserts+updates+limit - Postgres 9.3 |