Re: MOVE strangeness

"Jeroen T. Vermeulen" <jtv(at)xs4all(dot)nl> writes:
> Okay, given that, is there really any reason why MOVE should return the
> number of rows that would have been fetched? Why not report the number
> of rows moved? Having two different MOVE commands from the same starting
> positions yield indistinguishable results yet bring you to different
> states is very, very awkward and possibly quite useless. Better yet,
> why should FETCH report the number of rows fetched instead of the
> number of rows moved when you're going to extract the former from the
> PQresult's PQntuples() anyway?

The main reason why neither of these are likely to change is that it
will break existing, working applications if we change it. "Why not"
is not an argument that will win out against that point ... especially
not when it's debatable whether the proposed change is actually an
improvement.

regards, tom lane