SQL Server JDBC - RE: "varbinary(max)" data type is returning as "image" in MS SQL

Author

RE: "varbinary(max)" data type is returning as "image" in MS SQL

Sagar

2006-03-05, 8:24 pm

Hi Yesim,
Thanks for response. Couple of more issue I have found during using MS SQL
2005 drivers.

1. getProcedures of DatabaseMetaData doesn't return procedure name
correctly. for e.g. it returns "procName;1" for procedure name "procName".
2. For some of datatype such as smallmoney, timestamp and uniqueidentifier
driver return as smallmoney(10,4), timestamp(8) and uniqueidentifier(36)
.
Please note that column size with precision doesn't make in sense in these
data type.

I would appriciate if you can verify those and let me know if those are bugs?
Let me know if you need any more info from my side. Also let me know how I
can file a bug directly for MS SQL 2005 driver?

Thanks,
Sagar

"Yesim Koman" wrote:

> Hi Sagar,
>
> Thank you for your input. We've verified that the issue you've run into is
> indeed a bug. I will get back to you once we internally decide on when a
> fix will be available. Thanks for your patience,
>
> Yesim
>
>

Joe Weinstein

2006-03-05, 8:24 pm

Sagar wrote:

> Hi Yesim,
> Thanks for response. Couple of more issue I have found during using MS SQL
> 2005 drivers.
>
> 1. getProcedures of DatabaseMetaData doesn't return procedure name
> correctly. for e.g. it returns "procName;1" for procedure name "procName".
> 2. For some of datatype such as smallmoney, timestamp and uniqueidentifier
> driver return as smallmoney(10,4), timestamp(8) and uniqueidentifier(36)
.
> Please note that column size with precision doesn't make in sense in these
> data type.
>
> I would appriciate if you can verify those and let me know if those are bugs?
> Let me know if you need any more info from my side. Also let me know how I
> can file a bug directly for MS SQL 2005 driver?

Hi. Actually if you know SQLServer details, those are all informative
returns. It is little known, but there can be different versions of the
same-named stored procedure in the DBMS, and the ;1 suffix indicates it's
the first version. You could actually use that whole name in SQL, and even
call superceded versions, but for most users, it is not commonly seen.
The numeric suffixes to the data types are also correct, if redundant in
some cases. A unique identifier *is* a 36-byte entity, always (currently) so
at least for now the suffix could be assumed. The same with a timestamp
which is internally an 8-byte varbinary column, etc.
HTH,
Joe Weinstein at BEA Systems
[color=darkred]
>
> Thanks,
> Sagar
>
> "Yesim Koman" wrote:
>
>

Yesim Koman

2006-03-09, 8:23 pm

Hi Sagar,

Thanks a lot for the feedback. We are going to investigate the two new
issues you've brought up and get back to you as soon as we have answers on
these issues.

With regards to your original question on varbinary(max) datatype returning
as image, we have determined that the underlying bug is a SQL Server system
stored procedures issue. We filed a bug against the server and we are going
to track it. However, we will not be able to fix our driver's behavior
until the server produces a fix for the underlying issue. We will follow up
on this post once a fix is available.

Unfortunately, you cannot file bugs directly for SQL 2005 driver. However,
we would be more than happy to file bugs on your behalf if you provide us
with detailed descriptions of the behavior you are observing. Thanks,

Yesim

Sponsored Links