Re: DBCOLUMNFLAGSENUM
From: Darren Green (darren.green_at_reply-to-newsgroup-sqldts.com)
Date: 03/09/04
- Next message: Lontae Jones: "Append to exisiting Text File"
- Previous message: haseeb: "Re: transaction log backup job failed"
- In reply to: Gary Ewen: "DBCOLUMNFLAGSENUM"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 9 Mar 2004 19:15:27 +0000
In message <2905AFDE-9EC3-4E40-A238-015A0DE5B20B@microsoft.com>, Gary
Ewen <anonymous@discussions.microsoft.com> writes
>I have been writing a generic import program based on the code
>generated by SQL Server DTS.
>BOL claimed that the flags property of the column object could be broken
>down using the following enumeration...
>enum DBCOLUMNFLAGSENUM
> { DBCOLUMNFLAGS_ISBOOKMARK = 0x1,
> DBCOLUMNFLAGS_MAYDEFER = 0x2,
DBCOLUMNFLAGS_WRITE = 0x4,
DBCOLUMNFLAGS_WRITEUNKNOWN = 0x8,
DBCOLUMNFLAGS_ISFIXEDLENGTH = 0x10,
DBCOLUMNFLAGS_ISNULLABLE = 0x20,
DBCOLUMNFLAGS_MAYBENULL = 0x40,
DBCOLUMNFLAGS_ISLONG = 0x80,
DBCOLUMNFLAGS_ISROWID = 0x100,
DBCOLUMNFLAGS_ISROWVER = 0x200,
DBCOLUMNFLAGS_CACHEDEFERRED = 0x1000
} ;
The problem I have, is that when I generate import code using SQL Server,
it set the flag property of one of my columns to 592. Am I a fool? It would
seem to me that this isn't possible using the specified enumeration. Is
there a newer version of this enum which my BOL doesn't know about?
Thanks in advance....
Here's some SQL that says 592 is made up of DBCOLUMNFLAGS_ISFIXEDLENGTH,
DBCOLUMNFLAGS_MAYBENULL and DBCOLUMNFLAGS_ISROWVER. I just used SQL
because it is easy to knock up such tests.
DECLARE @DBCOLUMNFLAGS_ISBOOKMARK int
DECLARE @DBCOLUMNFLAGS_MAYDEFER int -- 0x2,
DECLARE @DBCOLUMNFLAGS_WRITE int -- 0x4,
DECLARE @DBCOLUMNFLAGS_WRITEUNKNOWN int -- 0x8,
DECLARE @DBCOLUMNFLAGS_ISFIXEDLENGTH int -- 0x10,
DECLARE @DBCOLUMNFLAGS_ISNULLABLE int -- 0x20,
DECLARE @DBCOLUMNFLAGS_MAYBENULL int -- 0x40,
DECLARE @DBCOLUMNFLAGS_ISLONG int -- 0x80,
DECLARE @DBCOLUMNFLAGS_ISROWID int -- 0x100,
DECLARE @DBCOLUMNFLAGS_ISROWVER int -- 0x200,
DECLARE @DBCOLUMNFLAGS_CACHEDEFERRED int -- 0x1000
SET @DBCOLUMNFLAGS_ISBOOKMARK = 0x1
SET @DBCOLUMNFLAGS_MAYDEFER = 0x2
SET @DBCOLUMNFLAGS_WRITE = 0x4
SET @DBCOLUMNFLAGS_WRITEUNKNOWN = 0x8
SET @DBCOLUMNFLAGS_ISFIXEDLENGTH = 0x10
SET @DBCOLUMNFLAGS_ISNULLABLE = 0x20
SET @DBCOLUMNFLAGS_MAYBENULL = 0x40
SET @DBCOLUMNFLAGS_ISLONG = 0x80
SET @DBCOLUMNFLAGS_ISROWID = 0x100
SET @DBCOLUMNFLAGS_ISROWVER = 0x200
SET @DBCOLUMNFLAGS_CACHEDEFERRED = 0x1000
PRINT 'What options are on?'
PRINT @DBCOLUMNFLAGS_ISBOOKMARK & 592
PRINT @DBCOLUMNFLAGS_MAYDEFER & 592
PRINT @DBCOLUMNFLAGS_WRITE & 592
PRINT @DBCOLUMNFLAGS_WRITEUNKNOWN & 592
PRINT @DBCOLUMNFLAGS_ISFIXEDLENGTH & 592
PRINT @DBCOLUMNFLAGS_ISNULLABLE & 592
PRINT @DBCOLUMNFLAGS_MAYBENULL & 592
PRINT @DBCOLUMNFLAGS_ISLONG & 592
PRINT @DBCOLUMNFLAGS_ISROWID & 592
PRINT @DBCOLUMNFLAGS_ISROWVER & 592
PRINT @DBCOLUMNFLAGS_CACHEDEFERRED & 592
PRINT ''
PRINT 'Confirm'
PRINT @DBCOLUMNFLAGS_ISFIXEDLENGTH + @DBCOLUMNFLAGS_MAYBENULL +
@DBCOLUMNFLAGS_ISROWVER
-- Darren Green (SQL Server MVP) DTS - http://www.sqldts.com PASS - the definitive, global community for SQL Server professionals http://www.sqlpass.org
- Next message: Lontae Jones: "Append to exisiting Text File"
- Previous message: haseeb: "Re: transaction log backup job failed"
- In reply to: Gary Ewen: "DBCOLUMNFLAGSENUM"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|