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