Skip to Content.
Sympa Menu

freetds - Re: [freetds] Server - Problems with TDS 4.2 COLFMT token

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "James K. Lowden" <jklowden AT schemamania.org>
  • To: FreeTDS Development Group <freetds AT lists.ibiblio.org>
  • Subject: Re: [freetds] Server - Problems with TDS 4.2 COLFMT token
  • Date: Sun, 16 May 2004 14:33:23 -0400

On Sat, 15 May 2004, Steve Kirkendall <skirkendall AT dsl-only.net> wrote:
> 3) For "timestamp", the SQL_DATETIME_SUB and INTERVAL_PRECISION columns
> in sp_datatype_info's result table are null. So that probably isn't
> why Crystal Reports is truncating timestamps at 8 characters. One
> weird thing: your server reports "timestamp" as being generic binary
> (type code -2) instead of ODBC timestamp (type code 11).

If you look in the ML archives, you'll find a short thread a few months
ago about timestamp data as it relates to BCP. IIRC, the only way a
client knows it's got a timestamp column -- as opposed to, say, a generic
binary -- is that the server sets the usertype to 50. You'll find some
brief mentions of that in Sybase's TDS functional specs, and, less
plainly, in Microsoft's documentation.

--jkl




Archive powered by MHonArc 2.6.24.

Top of Page