Re: JDBC_FreeResult - Free resultset and preparedStatement -- RPG400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

I don't agree with your assessment.

It closes the current statement -- i.e. it releases the database resources it's currently using, so the database manager will stop processing the SQL statement that you executed, and free up it's memory.

It doesn't free the PreparedStatement object you created! It doesn't prevent you from inserting new parameter markers and running it again! It just closes the previous run so you aren't running BOTH.

On 9/8/2010 9:51 AM, hockchai Lim wrote:

I just did some studying on Scott Klement's JDBC_FreeResult export
procedure. In observing the code, it seems like this procedure not only
closes and frees the ResultSet, it also auto closes and frees the
PreparedStatement object that is associated to the ResultSet.

I've wrote a RPG program that needs to a same PreparedStatment object to
perform different queries using different parameter mark values. So, I
really do not want to free the PreparedStatement object when freeing the
ResultSet. Does anyone know of the best way to handle this?

Thanks

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.