Re: java.lang.OutOfMemoryError - Mailing list pgsql-jdbc

From Barry Lind
Subject Re: java.lang.OutOfMemoryError
Date
Msg-id 3E416432.8020606@xythos.com
Whole thread Raw
In response to Re: java.lang.OutOfMemoryError  (snpe <snpe@snpe.co.yu>)
Responses Re: java.lang.OutOfMemoryError  (snpe <snpe@snpe.co.yu>)
List pgsql-jdbc

snpe wrote:
> But, I can't commit or rollback, does it ?
> If I have to care for query, commit or rollback I can simple use declare cursor
> and I am sure what I do.
> I think that is only solution - cursor out of a transaction.
> It shouldn't be problem with MVC.
> Oracle have cursor out of a transaction and OLTP systems with tousend user.
> It isn't possible any multi database project without this features
>
> Thanks Barry
> Haris Peco
>

The fact that cursors are constrained to a single transaction is not a
jdbc issue.  That is how postgresql works on the server.  If you want
that behavior changed, then this is the wrong email list to make those
requests.  Better yet, since this is open source code, the best way to
get anything changed is to code the changes yourself and submit them
back to the community.

That being said, it is certainly within the jdbc spec for cursors not to
extend across transactions.  That is why the meta data classes have
methods for the client to inquire if the server supports cursors across
transactions.

thanks,
--Barry




pgsql-jdbc by date:

Previous
From: snpe
Date:
Subject: Re: java.lang.OutOfMemoryError
Next
From: snpe
Date:
Subject: Re: java.lang.OutOfMemoryError