FIX: JDBC Driver Overwrites Timestamp Parameter Values with the Last Value Set (818504)
The information in this article applies to:
- Microsoft SQL Server 2000 Driver for JDBC
SYMPTOMSWhen the Microsoft SQL Server 2000 Driver for JDBC is used
to set values for multiple Timestamp parameters that are bound to the same Timestamp object, the driver overwrites all such values with the value set
for the last Timestamp parameter on execution of the query.CAUSEA bug in the driver causes this problem. Because the same
bound object is used for all the parameters, the driver internally overwrites
the previous value. This bug also affects Time parameters.RESOLUTION A supported fix is now available from
Microsoft, but it is only intended to correct the problem described in this
article. Only apply it to systems that are experiencing this specific problem.
This fix may receive additional testing to further ensure product quality.
Therefore, if you are not severely affected by this problem, Microsoft
recommends that you wait for the next service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product
Support Services to obtain the fix. For a complete list of Microsoft Product
Support Services phone numbers and information about support costs, visit the
following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for
support calls may be canceled if a Microsoft Support Professional determines
that a specific update will resolve your problem. The usual support costs will
apply to additional support questions and issues that do not qualify for the
specific update in question.
The English version of this
fix has the file attributes (or later) that are listed in the following table.
The dates and times for these files are listed in coordinated universal time
(UTC). When you view the file information, it is converted to local time. To
find the difference between UTC and local time, use the Time
Zone tab in the Date and Time tool in Control Panel.
The Windows version of this fix has the following properties:
Date Time Version Size File name
--------------------------------------------------------------
02-Apr-2003 17:44 2.2.0033 286,787 Msbase.jar
02-Apr-2003 17:44 2.2.0033 67,040 Mssqlserver.jar
02-Apr-2003 17:44 2.2.0033 58,903 Msutil.jar
The Unix-based version of this fix has the following properties:
Date Time Version Size File name
--------------------------------------------------------------
08-Apr-2003 18:53 2.2.0033 286,787 Msbase.jar
08-Apr-2003 18:53 2.2.0033 67,040 Mssqlserver.jar
08-Apr-2003 18:53 2.2.0033 58,903 Msutil.jar
Note Although the file dates are different for each operating system
that is listed, internally the files are exactly the same. The best way to
determine the version of the driver you are using is to use the getDriverVersion method of the DatabaseMetaData interface. WORKAROUNDBind each parameter to a new object instead of using the
same object for all the parameters. In some cases ths may not work around the
bug, specifically if you are using any wrapper classes for the JDBC API.
Internally those classes re-use the same object for setting the values for
different parameters.STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
Note Do not use this fix with the Microsoft virtual machine (Microsoft
VM). If you experience this problem, and you must have a fix that works with
virtual machine, contact Microsoft Product Support Services as described in the
"Resolution" section of this article.
Modification Type: | Minor | Last Reviewed: | 10/25/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbQFE kbfix kbbug KB818504 |
---|
|