My favorites | Sign in
Logo
                
New issue | Search
for
| Advanced search | Search tips
Issue 2: Expose realPreparedStatement
2 people starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  ----
Closed:  Feb 2009
Type-Defect
Priority-Medium


Sign in to add a comment
 
Reported by jrobertray, Dec 08, 2008
I'm working with a pre-1.6 oracle driver which doesn't have setNString.

To set a unicode value, I must get access to the raw
OraclePreparedStatement and call "setFormOfUse(n, FORM_NCHAR)" on it to
flip that column over to unicode.

When using log4jdbc, I see no way to gain access to the
"realPreparedStatement" (protected member) to accomplish this.

Please consider adding a get method to expose the raw prepared statement
for cases like this.
Comment 1 by arthur.blake, Feb 25, 2009
This will be added to the next alpha release (coming soon!)
Comment 2 by arthur.blake, Feb 26, 2009
This feature has been added to log4jdbc in the 1.2 alpha 2 release (see http://tinyurl.com/atnd4d)  would appreciate a message back here after you've tested 
and used this feature... thanks!
Status: Fixed
Sign in to add a comment

Hosted by Google Code