Skip to content

argument always null with stored procedure #77

Closed
quintonm opened this Issue Oct 12, 2013 · 2 comments

1 participant

@quintonm
p6spy member

Migrated from sourceforge: https://sourceforge.net/p/p6spy/bugs/18/

I use the trunk version from the SVN (2.0-SNAPSHOT) and when I look at the log I cannot see which values are passed to a stored procedure:
1275938874256|175|1|statement|{call WEB.GET_REM_SAI(?, ?)}|{call WEB.GET_REM_SAI(null, null)}
Nevertheless, it does work for the SELECT statement.
I didn't check the source to see where it could be wrong...

@quintonm quintonm was assigned Nov 7, 2013
@quintonm
p6spy member
quintonm commented Nov 7, 2013

This works in the latest snapshot version. However, only 'IN' parameters are resolved. 'OUT' parameters are still null.

@quintonm quintonm closed this Nov 7, 2013
@quintonm
p6spy member
quintonm commented Nov 7, 2013

The problem with out parameters is being tracked on #133.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.