]
[mailto:[EMAIL PROTECTED]] On Behalf Of chris markiewicz
Sent: September 6, 2001 2:58 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [JDBC] error - NOTICE: current transaction...MORE DETAIL...
spoke too soon. i see the error again (with 7.1) ...i
corrupted note necessarily the java connection wrapper.
Of course this is all guess work right now. I'll let you know if I
come up with a better solution or are able to determine why
these connections act like they are getting corrupt.
-Original Message-
From: chris markiewicz [mailto:[EMAIL
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 06, 2001 12:10 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: Re: [JDBC] error - NOTICE: current transaction...MORE DETAIL...
chris markiewicz [EMAIL PROTECTED
: Re: [JDBC] error - NOTICE: current transaction...MORE DETAIL...
chris markiewicz [EMAIL PROTECTED] writes:
i do agree that since everyone isn't complaining, the problem is likely in
my code. the odd thing is that i wasn't seeing this behavior with the 7.0
stuff, only with the 7.1.
Hmm
use of
these connections and am focusing my effort in that
direction right now.
Sure wish one of the experts would chime in on this.
t.r.
-Original Message-
From: chris markiewicz [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 06, 2001 7:17 AM
To: Missner, T. R.; [EMAIL PROTECTED
out there has some insight that could help.
t.r. missner
level(3) communications
-Original Message-
From: chris markiewicz [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 04, 2001 11:40 AM
To: [EMAIL PROTECTED]; 'Postgres Jdbc (E-mail)'
Cc: [EMAIL PROTECTED]
Subject: Re: [JDBC] error
the time to go through the code
but I will at some point.
I know someone out there has some insight that could help.
t.r. missner
level(3) communications
-Original Message-
From: chris markiewicz [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 04, 2001 11:40 AM
To: [EMAIL PROTECTED
Hello.
I have been having problems with postgresql large objects...i have been
searching the archives of this group and i have posted a question or two but
i have so far be unable to resolve the issues. right now, i have a screen
that loads a few LOs...they occasionally don't make it to the
hello. yet another follow-on to my questions...is there a way to determine
whether i am going to get this NOTICE before i execute a query? check
some status code or something?
thanks
chris
-Original Message-
From: Chris Markiewicz [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 04
i believe that when you close the stmt, the rs is automatically closed. you
have to leave the stmt open until you're done with the rs.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Mano lito
Sent: Tuesday, August 28, 2001 7:14 AM
To: [EMAIL PROTECTED]
I have exactly the same problem...it happens randomly, it seems. maybe 5%
of the time. also happens on selects (lo_read though). the only advice
that i've seen on the topic is to make sure that autocommit is set to false,
which i've done, but i still see the problem.
unfortunately, my next
Hello. I just update my driver to the latest version (7.1-1.3). I am
seeing MANY of the following exception:
No results were returned by the query.
at org.postgresql.jdbc2.Statement.executeQuery(Statement.java:63)
at
(Finalizer.java:163)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of chris markiewicz
Sent: Thursday, August 16, 2001 12:47 PM
To: [EMAIL PROTECTED]
Subject: [JDBC] No results exception on executeQuery()
Hello. I just update my driver to the latest version
While I can readily reproduce it on my application, I have so far been
unsuccessful at writing a test case that reproduces the problem.
Oh, I just tried the latest drivers - no luck - same problem.
Equally unfortunate is the fact that all database processing is heavily
abstracted in the
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of chris markiewicz
Sent: Thursday, August 02, 2001 6:04 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: [JDBC] errors while getting large objects...
hello.
my application uses large objects frequently...to render
hello.
my application uses large objects frequently...to render the main page, it
might load anywhere from zero to 10 large objects - mostly images or
documents. recently i started stress testing this page (making it always
load many LOs) and i frequently encounter two different problems.
1.
i have a different but related question - i OCCASIONALLY get a fastpath
error. i'd guess that it shows up once in every hundred LO requests. i've
verified that autocommit is set to false. the stack trace is shown here:
FastPath call returned ERROR: lo_tell: invalid large object descriptor
hello.
it seems that a null value in an integer (int4) column gets converted to
zero at some point...is this accurate? i look in the db and see null
(queried using IS NULL to make sure), but i call an rs.getObject(colName)
and get a java.lang.Integer with a value of zero...is this in jdbc or
18 matches
Mail list logo
