Re: Fix for fetchone() and fetchmany() in Python interface

> Bruce,
>
> It may be too late for including it, but it would not be for the reasons above.
>
> 1) low risk
>
> It is low risk. It is a one line patch that only affects the python interface code.
>
> 2) major
>
> It is major. Without it we can consider that 7.1 does not support Python
> (at least, not the 2.0 API).
>
> What use is an interface that keeps returning the same row (the first one)
> every time you call the cursor trying to get the next row?
>
> It happens with both functions fetchone() and fetchmany(), so there is no
> workaround besides reading the whole table (which sometimes is not feasible).
>
>
> So, it is both low risk and major.

If it has taken months for someone report report it and fix it, it can't
be that major.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026