Can you please try the current beta from our ftp site. I think this is
fixed in 7.1beta.
> Jason Southern ([EMAIL PROTECTED]) reports a bug with a severity of 2
> The lower the number the more severe it is.
>
> Short Description
> JDBC PreparedStatement.setMaxRows() affects other objects intan
> ... Should we print the "days" +/-
> sign only when it is not the same as the "year" sign? Seems like the
> way to go.
It isn't quite that easy, but you have the right idea. My new code omits
signs unless there is a negative field value, then all subsequent fields
are signed.
That seems to be
Christian Gonzalez ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
Query Problem!!
Long Description
I have problem with the GROUP BY
Sample Code
select name, 'user' as class from smuser union select name, 'group' as class from
Wow, this was interesting. I never suspected that in:
-1 year 360 days 00:00
the "360 days" is positive, while the "-1 year" was negative, but I can
now see how that can very easily happen. Should we print the "days" +/-
sign only when it is not the same as the "year" sign? Seems lik
Bruno Wolff III <[EMAIL PROTECTED]> writes:
> The query below used to work with 7.0.3. If I change 'lower(title)' to
> 'title' in the order by clause, then the query is accepted.
> area=> select code, wbc.gameid, title from games, wbc where wbc.gameid =
>games.gameid union select code, null, nul
Jason Southern ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
JDBC PreparedStatement.setMaxRows() affects other objects intantiated from this class
and it's parent class
Long Description
==
James Troup <[EMAIL PROTECTED]> writes:
> | template1=# create table x (y int4); insert into x values (31); select y,
>int4out(y) from x;
> | CREATE
> | INSERT 34029 1
> | y | int4out
> | +---
> | 31 | 136420312
> | (1 row)
The bug here is that the system allows you to inv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hello,
we noticed a bug occuring when using Postgresql 7.0 on NT as well on Linux
and Solaris...
we get the following error:
Bad Integer N
> > at org.postgresql.jdbc2.ResultSet.getInt(ResultSet.java:454)
> > at org.postgresql.jdbc2.ResultSet.g
> Secondly, we have a problem with interval math, detailed below. Should
> be reproducible on any platform(?)
> Version: 7.0.2 (is it fixed in the latest?)
Yes, but may need a little more fixup...
> =# select '2 years ago'::interval + '1 year 360 days 00:00'::interval;
>?column?
> -
