Re: Having a plpgsql function return multiple rows that indicate its progress in a cursor like fashion
| От | Peter Geoghegan |
|---|---|
| Тема | Re: Having a plpgsql function return multiple rows that indicate its progress in a cursor like fashion |
| Дата | |
| Msg-id | db471ace1002161240w6d145916ia1952b3ef9c5a5ef@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Having a plpgsql function return multiple rows that indicate its progress in a cursor like fashion (Alvaro Herrera <alvherre@commandprompt.com>) |
| Ответы |
Re: Having a plpgsql function return multiple rows that
indicate its progress in a cursor like fashion
|
| Список | pgsql-general |
> We've had several requests for progress reporting thingies of all kinds. > The amount of effort is not insignificant, which is probably why nothing > has gotten done yet ... What do you mean by "reporting thingies of all kinds"? It isn't as if I'm asking for some esoteric feature, some regional variation of reporting on batch operations. I'd like to be able to report things back to client apps. That would perhaps take the form of returning a message string, and an integer at each RETURN NEXT (or whatever mechanism is decided upon). It would probably still be very useful to a lot of people if the feature was completely inflexible, not allowing you to vary the RETURN NEXT datatype, for example. Can't someone think of a way of doing this as a neat adjunct to Postgres? Thanks, Peter Geoghegan
В списке pgsql-general по дате отправления: