Bug #11310 CallableStatementSapDB.handleStreamsForExecute inefficient
Submitted: 14 Jun 2005 11:22 Modified: 27 Sep 2008 12:55
Reporter: Markus Kohler Email Updates:
Status: Won't fix Impact on me:
Category:MaxDB Severity:S2 (Serious)
Version: OS:Microsoft Windows (Windows)
Assigned to: Ulf Wendel CPU Architecture:Any

[14 Jun 2005 11:22] Markus Kohler
Within the jdbc driver, the implementation of 
CallableStatementSapDB.handleStreamsForExecute  seems to be inefficient. 
My profiler tells me that for my particular test case a ClassCastException is thrown (and handled) 43132 times in this method.


How to repeat:
Just look at the source. 

Suggested fix:
I guess just checking for the class should be faster (and less ugly).
[16 Jun 2005 16:33] Ulf Wendel
Thanks for the pointer Markus,

we'll have a look at it. I'll keep you posted with the answer from the development team.

Best regards,
[17 Jun 2005 8:05] Ulf Wendel
Hello Markus,

the developers have appreciated your hint very much. They promised to provide a fix with one of the next releases of the current 7.5/7.6 versions. 

Thanks for pointing us to this flaw!
[27 Sep 2008 12:55] Konstantin Osipov
MaxDB is no longer under MySQL umbrella.