Hi All,

In Ingres2.6 the sum() operation on a set of integers always returned an
int4 item...which was cool for the java applications we have written.

Since upgrading to Ingres2006, we now see that the sum() returns an int8
item. This is unfortunate as it doesn't need to and our java apps throw
an cast exception error as the fields are returned as a Java Long (long
integer) type instead of an Integer (regular integer) type that the code
expects.

The values being summed never need to be stored as a long int (they are
never big enough).

The query could be rewritten to explictly convert the result of the
calculation to an int4 (i.e. select int4(sum(field) as ...). However
that would mean rewriting quite a lot of SQL hence a degree of risk.

Is there some configuration parameter (DBMS or per-database) that could
force the default type of sum() (and other aggregates) to be integer4?

Martin Bowes

On Feb 20, 2009, at 8:02 AM, Martin Bowes wrote:

Nope. If the client side is 2.6 or older, a coercion is applied
to some i8 items to make them i4; I know it happens with tids, and
I think sum() would qualify as well. However in the jdbc situation,
the dbms server client is the DAS server, which is up to date.
So the down-coercion wouldn't apply.

Karl

Thanks Karl,

Marty

-----Original Message-----
From: info-ingres-bounces (AT) kettleriver...ting (DOT) com
[mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of Karl
& Betty Schendel
Sent: 20 February 2009 15:39
To: Ingres and related product discussion forum
Subject: Re: [Info-Ingres] default type of a sum()


On Feb 20, 2009, at 8:02 AM, Martin Bowes wrote:

Nope. If the client side is 2.6 or older, a coercion is applied
to some i8 items to make them i4; I know it happens with tids, and
I think sum() would qualify as well. However in the jdbc situation,
the dbms server client is the DAS server, which is up to date.
So the down-coercion wouldn't apply.

Karl

_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://www.kettleriverconsulting.com...fo/info-ingres

Hi Marty,
there was a similar problem for some ODBC applications. In ODBC there
is now a connection flag available which forces the conversion from
all int8 to int4 in the Driver. Not sure whether we can add this to
the JDBC driver too, but you can open an issue and we will check. Keep
in mind that if this conversion is place you can not retrieve "real"
int8 values in this session.

Kristoff