sql query cursor problem
От | Risko Peter |
---|---|
Тема | sql query cursor problem |
Дата | |
Msg-id | Pine.LNX.4.21.0107090825110.347-101000@ris.mhc обсуждение исходный текст |
Ответы |
Re: sql query cursor problem
|
Список | pgsql-bugs |
============================================================================ POSTGRESQL BUG REPORT TEMPLATE ============================================================================ Your name : Peter RISKO Your email address : rpetike@freemail.hu System Configuration --------------------- Architecture (example: Intel Pentium) : Intel Pentium III Operating System (example: Linux 2.0.26 ELF) : Linux 2.4.3 PostgreSQL version (example: PostgreSQL-7.0): PostgreSQL-7.1.1 Compiler used (example: gcc 2.8.0) : gcc 2.95.2 Please enter a FULL description of your problem: ------------------------------------------------ Dear list members, We are developing an application that uses Postgresql as its dbms. It seems we've found a bug in PostgreSQL handling of cursored queries. I assume that it's legal to do 'fetch backward all in xxx' and then 'fetch 1 in xxx' afterwards. If it is not legal in Postgresql, the rest of this mail is irrelevant. (I have been using Postgresql for quite a long time now, and I experienced that you cannot 'fall off' of neither ends of a query result by moving the cursor.) Please describe a way to repeat the problem. Please try to provide a concise reproducible example, if at all possible: ---------------------------------------------------------------------- So the bug appears when I execute the following steps: 1. in psql shell: => create database test; => create user tester with password 'tester'; 2. in the os's shell: $ psql -d test -U tester -f ss3.sql $ psql -d test -U tester 3. in psql shell: => \i test5a.sql => fetch 1 in lionhart; => fetch -1 in lionhart; => fetch 1 in lionhart; ??? last fetch should return a row, but it doesn't seem like... Attached files: ss3.sql : The dumped content of my database test5a.sql : The query we would use If you know how this problem might be fixed, list the solution below: ---------------------------------------------------------------------
В списке pgsql-bugs по дате отправления: