Re: some error in table definition
- From: "Roy Harvey (SQL Server MVP)" <roy_harvey@xxxxxxxx>
- Date: Tue, 30 Oct 2007 11:54:31 GMT
On Tue, 30 Oct 2007 10:35:08 -0000, cong <franzcai80@xxxxxxxxx> wrote:
IS_ORIGIONAL bit NOT NULL,
CONSTRAINT DF_BBSItem_IS_ORIGIONAL DEFAULT(0),
AUTHOR nvarchar(15) COLLATE Chinese_PRC_CS_AS NOT NULL,
row 9:ITEM_CONTENT nvarchar(3000) COLLATE Chinese_PRC_CS_AS NOT NULL,
constraint 'TABLE' definition wrong in gramma??
A constraint that comes after a comma is a table constraint. Table
constraints must be specified AFTER all the columns. Since this is a
DEFAULT constraint that must be associated with a column remove the
comma and make it a column constraint.
BROWSED_TIMES smallint NOT NULL
CONSTRAINT DF_BBSItem_BROWSED_TIMES DEFAULT(0),
LATEST_REPLICATION_ID int NULL
When you get past that you will find that CLUSTERD is not the correct
spelling of the keyword CLUSTERED. And you might prefer to spell
ORIGIONAL as ORIGINAL, and if REPLYD is supposed to be the past tense
of REPLY then you might want REPLYED.
Roy Harvey
Beacon Falls, CT
.
- Follow-Ups:
- Re: some error in table definition
- From: cong
- Re: some error in table definition
- From: Erland Sommarskog
- Re: some error in table definition
- References:
- some error in table definition
- From: cong
- some error in table definition
- Prev by Date: Re: Error message on using union statement with order by using reserved words
- Next by Date: Re: CONTAINS and wildcard
- Previous by thread: some error in table definition
- Next by thread: Re: some error in table definition
- Index(es):