Long(1));
ResultSet rs2=s2.executeQuery();
while(rs2.next()) {
System.out.println(rs2.getLong(1) + " " + rs2.getString(2));
}
rs2.close();
s.close();
ones.
Here's the stacktrace:
Bad Long
at org.postgresql.jdbc2.ResultSet.getLong(ResultSet.java:284)
at Test.go(Test.java:35)
at Test.main(Test.java:15)
I'm using the 7.0.2 JDBC drivers against the 7.1beta1 backend and
everything seems to be working fine.
Stu.
--
Stu Coates
Chelmsfo
g on the
lists [HACKERS mainly] from Peter for a while.
Stu.
--
Stu Coates
Chelmsford, England U.K.
ICQ:146628
http://www.stucoates.com/
__
FREE Personalized Email at Mail.com
Sign up at http://www.mail.com/?sr=signup
n problem, and have discovered
another. Attached is a short shell script that causes pg_dump to core
dump whilst trying to dump a single, quite simple, table.
Stu.
--
Stu Coates
Chelmsford, England U.K.
http://www.StuCoates.com/
The day Microsoft makes something that doesn't suck is pro
Tom Lane wrote:
>
> Stu Coates <[EMAIL PROTECTED]> writes:
> > Anyway, I've sorted my obsolete version problem, and have discovered
> > another. Attached is a short shell script that causes pg_dump to core
> > dump whilst trying to dump a single, quite simple
Tom Lane wrote:
>
> Stu Coates <[EMAIL PROTECTED]> writes:
> > I come from an Oracle background where I can lock an item of data by
> > performing a "SELECT FOR UPDATE" on the row. This is also implemented
> > in PostgreSQL. A quite useful feature Orac
