Re: check constraints and null values
From: Gail Erickson [MS] (gaile_at_online.microsoft.com)
Date: 01/14/05
- Next message: Gert-Jan Strik: "Re: Composite Index?"
- Previous message: Jaco: "Re: Unique ID"
- In reply to: David Portas: "Re: check constraints and null values"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 14 Jan 2005 10:23:57 -0800
If you have not already done so, please use the doc feedback tool (the
little envelope) on the upper left hand corner of the incorrect topic so
that we can get this corrected.
Thanks,
-- Gail Erickson [MS] SQL Server Documentation Team This posting is provided "AS IS" with no warranties, and confers no rights "David Portas" <REMOVE_BEFORE_REPLYING_dportas@acm.org> wrote in message news:F_GdnVEnYZkCA3jcRVn-2w@giganews.com... > You are right. Books Online has it wrong. > mk:@MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\architec.chm::/8_ar_da_0777.htm > > SQL Server follows the ANSI / ISO Standard behaviour for CHECK and FOREIGN > KEY constraints: values that are *not FALSE* are permitted. I think it's > safe to assume that the designers' intention was that this should be the > case and that Books Online is in error :-). > > -- > David Portas > SQL Server MVP > -- > >
- Next message: Gert-Jan Strik: "Re: Composite Index?"
- Previous message: Jaco: "Re: Unique ID"
- In reply to: David Portas: "Re: check constraints and null values"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
