× 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.



<snip>
I don't know why that works that way. I'm confident this was something I
added deliberately, after the fact... I went to some sort of extra
pain to add that code... and I don't know why I did that, anymore.
</snip>

Scott, have you been following the thread on program comments and
documentation? :)


Paul Therrien
Andeco Software, LLC
2233 St. Charles Ave
# 704
New Orleans, LA 70130
225-229-2491
paultherrien@xxxxxxxxxxxxxxxxxx
www.andecosoftware.com

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Scott Klement
Sent: Sunday, March 25, 2012 9:40 PM
To: RPG programming on the IBM i / System i
Subject: Re: JDBCR4 and JDBC_FreeResult

Alan,

I wasn't deliberately ignoring you, but over the past week or so, I've had
several "crunch times" where I was just crazy busy... and I'm afraid your
e-mail just slipped through the cracks. (You know, the cracks in my brain!)

I don't know why that works that way. I'm confident this was something I
added deliberately, after the fact... I went to some sort of extra
pain to add that code... and I don't know why I did that, anymore.
(Perhaps also due to cracks in my brain?)

Anyway, you have the source code, so you should be able to remove that and
see if it causes any problem?

-SK



On 3/23/2012 3:28 PM, Alan Campin wrote:
I am using Scott's JDBC service and having a problem with
JDBC_FreeResult. When I call this function after I make a
JDBC_ExecPrepQry and JDBC_NextRow, the next time I try use my
statement object the program crashes and when I check I find that the
statement object has been destroyed.

When I look at the JDBC_FreeResult function I see that it destroys the
statement object in addition to releasing the result object. I believe
this is a bug. The big problem with this is that when you examine the
statement object in the RPG debugger the object still shows as being
valid but the object has been destroyed in the Java run time.

Scott I sent this your feedback but didn't hear anything so posting here.

P JDBC_FreeResult...
P B export
D JDBC_FreeResult...
D PI
D rs like(ResultSet)
D stmt s like(Statement)
/free
stmt = rs_getStatement(rs);
stmt_close(stmt);<<--------------
DeleteLocalRef(JNIENV_P: rs);
DeleteLocalRef(JNIENV_P: stmt);<<--------------
rs = *NULL;
/end-free
P E

--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.