Re: Weird problem with aggregate functions

Tom Lane wrote:
>
> "Andrea Aime" <aaime(at)comune(dot)modena(dot)it> writes:
> > Thanks, it works!!! But why doesn't it work without the
> > cast? This is a good workaround, but the standard behaviour
> > is a bug, isn't it?
>
> No, it isn't. We *used* to return int4 as the result of sum(int4),
> etc, but that tends to suffer from overflow. And the deficiency of
> using int4 as the result of avg() should be pretty obvious ;-)
>

[snip]

> >From what I've heard, VB simply does not recognize Postgres' NUMERIC
> datatype at all. I don't know if that's VB's fault or a problem in
> our ODBC driver.

It seems a problem of neither VB nor our ODBC driver.
We would get the expected result unless we use Microsoft
Cursor Service by setting the CursorLocation property
as adUseClient.
Unfortunately we couldn't get an updatable recordset using
ADO unless we use Microsoft Cursor Service.

regards,
Hiroshi Inoue