-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 
Author Message
 Post subject: Changing the prepared statement creation behaviour?
PostPosted: Sun Jun 05, 2005 7:26 pm 
Newbie

Joined: Sun Jun 05, 2005 7:01 pm
Posts: 1
Location: Gävle, Sweden
Hello,
Is there a clean way of affecting the prepared statement creation behaviour on save or update?
Background:
I'm using a WLS datasource and connection pool. I need to use a oracle.sql.STRUCT in a UserType and the WLS docs says that creating STRUCTS is "not supported" unless you get the underlying vendor connection using a getVendorConnection() call.
If I get the underlying vendor connection I get a penalty ("dirty" connections can't be returned to the pool), so I want to be a little bit smart about when I do this.

pseudo code:
if MyUserType.isdirty() then create PreparedStatement by using getVendorConnection() kind of thing...

I'm using a closed sourced library so there is no way coding around the oracle.sql.STRUCT :(.

Any ideas? Can events/interceptors be used or are they called too early/late?

Regards,
Johan


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.