db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From TomohitoNakayama <tomon...@basil.ocn.ne.jp>
Subject Re: [jira] Commented: (DERBY-1471) Implement layer B streaming for new methods defined in JDBC4.0
Date Tue, 14 Nov 2006 12:19:05 GMT
Hello.

Thank you.
I think the problem was solved using EmbedPreparedStatement :)

Best regards.

Knut Anders Hatlen wrote:

>TomohitoNakayama <tomonaka@basil.ocn.ne.jp> writes:
>
>  
>
>>Hello.
>>
>>Reading the code ( BaseMonitor.java, modules.properties,
>>InternalDriver.java and so on ), it seems that possible class of
>>engine is different between running environment ...
>>    
>>
>
>Yes, but the implementation of PreparedStatement.setBinaryStream(int,
>java.io.InputStream) is in EmbedPreparedStatement (not in
>EmbedPreparedStatement40) and therefore available to the network
>server regardless of environment. I think all that is needed is to put
>setBinaryStream(int, java.io.InputStream) into the
>EnginePreparedStatement interface, and it should be possible to invoke
>it from the network server.
>
>  
>
>>Then, I think it is needed to consider when the class is not expected class.
>>    
>>
>
>That's what the Engine* interfaces are there for. To see an example,
>you could look at how the EngineStatement interface is used in
>DRDAStatement to make the JDBC 3.0 methods getResultSetHoldability()
>and getMoreResults() available for a network server which is possibly
>running JDBC 2.0 only.
>
>  
>

-- 
/*

        Tomohito Nakayama
        tomonaka@basil.ocn.ne.jp
        tomohito@rose.zero.ad.jp
        tmnk@apache.org

        Naka
        http://www5.ocn.ne.jp/~tomohito/TopPage.html

*/ 


Mime
View raw message