| History |
| Case Num: 4315 Description: 08/18/2006 Fix of JDBC client handling of batching (determined by setFetchSize on the statement) results for CallableStatements. Fix for reading batches from connectors returning results for stored procedures. Usage Note: To avoid errors, CallableStatments should be created as scroll insensitive. Enhancement to allow the fetch size for procedures to be set as a connector binding property. To enable this property, an entry in the ConfigurationInfo.def or server config file is needed. For exmample: <Connector Name="My Sybase Connector" ComponentType="Sybase ANSI JDBC Connector" ... <Property Name="FetchSize">5000</Property> ... Sets a fetch size of 5000 for My Sybase Connector. This setting can be exposed for editing through the console by adding it to the appropriate component definition. For example: <ComponentType Name="Sybase ANSI JDBC Connector" ... <ComponentTypeDefn Deprecated="false"> <PropertyDefinition Name="FetchSize" DisplayName="Fetch Size" ShortDescription="Fetch Size For Procedure Execution." DefaultValue="0" Multiplicity="0..1" PropertyType="Integer" ValueDelimiter="," IsConstrainedToAllowedValues="true" IsExpert="true" IsHidden="false" IsMasked="false" IsModifiable="true" IsPreferred="false"/> </ComponentTypeDefn> ... Allows the fetch size to be edited for all Sybase ANSI JDBC Connectors |
| Case Num: 4580 Description: 09/11/2006 Fixed JDBC URL format error that would occur if a password passed as part of the JDBC URL contains the @ symbol. |
| Case Num: 4723 Description: 10/13/2006 Implements SQLState classes for connection, communication, logon, and session failures. This gives a connection pool the ability to detect when a connection should be considered stale. The state classes returned are 08001, 08S01, and 28000 depending on the failure. |
| Case Num: 4723 Description: 10/13/2006 Fixes an issue in where the client may not correctly be closing a connection if an exception is thrown while the connection is being shutdown. |
| Case Num: 4954 Description: 12/12/2006 Resolves issue where correct protocol was not getting passed to nested resources in the wsdl. |