Hello All,
I found an issue and wanted osme advice or guidance
I have found an issue in the ODBC API when getting the column type of a
BIGINT. When the column type is defined as BIGINT in the table then all
works fine. The column type is 127 (x7F) and size of 8 bytes
But if the I use convert to convert the column type eg ( convert(bigint,
colname ) ) or if I sum the column in a group by query the column type
returned is no 127 but 38 (x26) which is SQLINTN but the column size is 8
bytes.
The problem then arises when srv_setcoldata ,srv_setcollen and srv_sendrow
all fail.
If anyone has the xp_gettable_odbc source which comes with SQL Server and
tests the issue like this
master..xp_gettable_odbc '(select convert(bigint,0) as tt ) as dd'
no results will be returned but this
master..xp_gettable_odbc '(select convert(int,0) as tt ) as dd' will return
one row as it should
Has anyone else come across this issue if so any fixes?
Kind regards
Greg OHello Greg,
Based on my research, this seems to be a limitation of Open Data Service
(ODS). It only support 4 bytes int and there is no support of bigint.
You could refer to "Data types" topic in BOL for details.
http://msdn.microsoft.com/library/d...-us/odssql/ods_
6_ref_10_4n5k.asp
Hope this is helpful.
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
| From: "GregO" <grego@.community.nospam>
| Subject: ODBC Column Type Error with Bigint
| Date: Mon, 7 Nov 2005 18:52:42 +1100
| Lines: 29
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
| X-RFC2646: Format=Flowed; Original
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
| Message-ID: <uCLoZ#24FHA.1536@.TK2MSFTNGP10.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.programming
| NNTP-Posting-Host: dsl-202-173-157-78.vic.westnet.com.au 202.173.157.78
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.programming:129572
| X-Tomcat-NG: microsoft.public.sqlserver.programming
|
| Hello All,
| I found an issue and wanted osme advice or guidance
|
| I have found an issue in the ODBC API when getting the column type of a
| BIGINT. When the column type is defined as BIGINT in the table then all
| works fine. The column type is 127 (x7F) and size of 8 bytes
|
| But if the I use convert to convert the column type eg ( convert(bigint,
| colname ) ) or if I sum the column in a group by query the column type
| returned is no 127 but 38 (x26) which is SQLINTN but the column size is 8
| bytes.
|
| The problem then arises when srv_setcoldata ,srv_setcollen and
srv_sendrow
| all fail.
|
| If anyone has the xp_gettable_odbc source which comes with SQL Server and
| tests the issue like this
| master..xp_gettable_odbc '(select convert(bigint,0) as tt ) as dd'
|
| no results will be returned but this
| master..xp_gettable_odbc '(select convert(int,0) as tt ) as dd' will
return
| one row as it should
|
| Has anyone else come across this issue if so any fixes?
|
| Kind regards
| Greg O
|
|
|
Showing posts with label bigint. Show all posts
Showing posts with label bigint. Show all posts
Monday, March 19, 2012
Subscribe to:
Posts (Atom)