Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.es;
  h=Received:Subject:From:To:In-Reply-To:References:Content-Type:Date:Message-Id:Mime-Version:X-Mailer;
  b=iahpU3PbBN6yTO1YWS46K/+iWcSqmkLM3yj/u/qpH4XNF42EL2T5uElZed7vRQ13E89kclE9vxLpUNou+d9UMqOUhIXf1+U8thphHyDrm+rKOiGWp+iL6vemIR2mrQVM33wnWEs8nULcmC520yDE1lwT2clGM5RWmpj7e1eqB0M=
  ;
Subject: Re: Garbage Collector and memory
From: ji_villa <ji_villa@yahoo.es>
To: Derby Discussion <derby-user@db.apache.org>
In-Reply-To: <435E1D6D.1040300@sun.com>
References: <20051024093758.53836.qmail@web26207.mail.ukl.yahoo.com>
	 <435E1D6D.1040300@sun.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature"; boundary="=-ddGqIZWtD1lV+9qhb7cz"
Date: Thu, 27 Oct 2005 00:04:15 +0200
Message-Id: <1130364256.5227.14.camel@Hashut.casa>
Mime-Version: 1.0


--=-ddGqIZWtD1lV+9qhb7cz
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

El mar, 25-10-2005 a las 13:56 +0200, Fernanda Pizzorno escribi=C3=B3:
> Juan Ignacio Villa wrote:
>=20
> >[...]
> >
> >  Consulta =3D
> >DBConexion.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE,ResultSet.CON=
CUR_UPDATABLE);
> >  Rs =3D Consulta.executeQuery(sql);
> >
> >[...]
> >
> Hello,
>=20
> Scrollable sensitive result sets (ResultSet.TYPE_SCROLL_SENSITIVE) are=20
> not implemented
> in Derby. Scrollable insensitive result sets=20
> (ResultSet.TYPE_SCROLL_INSENSITIVE) are
> implemented in Derby, but only with concurrency ResultSet.CONCUR_READ_ONL=
Y.
>=20
> If your application needs updatable result sets (ie. if you are going to=20
> use updateXXX,
> updateRow(), insertRow() or deleteRow() methods), you will have to use=20
> forward only result
> sets (ResultSet.TYPE_FORWARD_ONLY), and you will only be able to move=20
> between rows in the
> result set using next().
>=20
> On the other hand, if you do not need to use updatable result sets, you=20
> can use scrollable
> insensitive result sets. The difference between this type and the one=20
> you are using is that
> it is not sensitive to changes to the underlying table.
>=20
> Since the result set type and concurrency you are trying to use are not=20
> implemented in
> Derby, the driver will generate a SQLWarning. And you can check the type=20
> and concurrency
> of the result set returned by the driver using ResultSet.getType() and
> ResultSet.getConcurrency() respectively.
>=20
> Fernanda
>=20

Thanks Fernanda. But i prove with ResultSet.TYPE_SCROLL_INSENSITIVE and
ResultSet.CONCUR_READ_ONLY and i get an out of memory error too.
Only works fine with ResultSet.TYPE_FORWARD_ONLY.

Statements or preparedStatements fail equals. Both give me the out of
memory error.

The code of Dyre (thaks Dyre) fails too.

System.gc also not free memory.
Catch exceptions not solve it.
Yes, bad code.

I am proving to resolve it.
=C2=BFIs extrange? Would be.

...and very thanks.

Villa.

--=-ddGqIZWtD1lV+9qhb7cz
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada
	digitalmente

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQBDX/1f5QuHnxGDAjERAhNMAKDMN2E0CQqs9VNCZ7jWZ7F2KPdlpgCfXS1C
yfE/AAtfXdZ6CnBrIlcQu+w=
=nvSr
-----END PGP SIGNATURE-----

--=-ddGqIZWtD1lV+9qhb7cz--


______________________________________________ 
Renovamos el Correo Yahoo! 
Nuevos servicios, m�s seguridad 
http://correo.yahoo.es