On 09/08/10 21:29, Heikki Linnakangas wrote:
On 09/08/10 21:26, Tom Lane wrote:
Heikki Linnakangas writes:
The behavior of empty arrays with dimensions is weird in general.
Agreed, but we shouldn't be introducing random restrictions in the name
of security.
Patch looks good to me, except tha
On 09/08/10 21:26, Tom Lane wrote:
Heikki Linnakangas writes:
The behavior of empty arrays with dimensions is weird in general.
Agreed, but we shouldn't be introducing random restrictions in the name
of security.
Patch looks good to me, except that it occurs to me to wonder about
negative va
Heikki Linnakangas writes:
> The behavior of empty arrays with dimensions is weird in general.
Agreed, but we shouldn't be introducing random restrictions in the name
of security.
Patch looks good to me, except that it occurs to me to wonder about
negative values of dim[i]. For small negative v
On 09/08/10 17:56, Tom Lane wrote:
writes:
I have the problem:
the code sending empty binary array works on 8.3 and 8.4
but stopped working on postgres 9.0 beta2/3/4, it fails with '22003','integer
out of range error'.
I think you are right --- this rejects dim[i] == 0, but it should not.
writes:
> I have the problem:
> the code sending empty binary array works on 8.3 and 8.4
> but stopped working on postgres 9.0 beta2/3/4, it fails with '22003','integer
> out of range error'.
I think you are right --- this rejects dim[i] == 0, but it should not.
regard
Hi,
I'm using libpq PQexecParams ability to send query parameters as binary data,
more specific - a binary representation of an empty array.
I have the problem:
the code sending empty binary array works on 8.3 and 8.4
but stopped working on postgres 9.0 beta2/3/4, it fails with '22003','intege
