Re: Modify the DECLARE CURSOR command tag depending on the scrollable flag
От | Tom Lane |
---|---|
Тема | Re: Modify the DECLARE CURSOR command tag depending on the scrollable flag |
Дата | |
Msg-id | 21369.1385240486@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Modify the DECLARE CURSOR command tag depending on the scrollable flag (Boszormenyi Zoltan <zb@cybertec.at>) |
Ответы |
Re: Modify the DECLARE CURSOR command tag depending on
the scrollable flag
|
Список | pgsql-hackers |
Boszormenyi Zoltan <zb@cybertec.at> writes: > Attached is the patch that modified the command tag returned by > the DECLARE CURSOR command. It returns "DECLARE SCROLL CURSOR" > or "DECLARE NO SCROLL CURSOR" depending on the cursor's > scrollable flag that can be determined internally even if neither is > asked explicitly. This does not strike me as an acceptable change. It will break any code that's expecting the existing command tag, for little or no benefit to most applications. Even if backwards compatibility were of no concern, I'm not convinced it's a good thing to expose the backend's internal choices about query plans used for cursors, which is what this is basically doing. > It is expected by the ECPG cursor readahead code. And that doesn't sound like a sufficient excuse. You should only assume a cursor is scrollable if SCROLL was specified in the cursor declaration command, which it'd seem to me is something ECPG would or easily could know about commands it issues. regards, tom lane
В списке pgsql-hackers по дате отправления: