Re: "varbinary(max)" data type is returning as "image" in MS SQL
- From: Joe Weinstein <joeNOSPAM@xxxxxxx>
- Date: Wed, 01 Mar 2006 07:53:31 -0800
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
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
.
- Next by Date: Re: Bug with Multiple Result Sets?
- Next by thread: RE: "varbinary(max)" data type is returning as "image" in MS SQL
- Index(es):
Relevant Pages
|