Hi,
Specifying the uniqueness and primary key constraints as table constraints
instead of column constraints works in both InstantDB and SQL Server (and is
SQL-92 compliant).
Johan
Peter Hearty wrote:
> Johan
>
> In this case, SQL Server is the compliant database. IDB does this so as
> to be able to import data from databases which do not enforce PK
> uniqueness.
>
> Pete
>
> ----- Original Message -----
> From: Johan Stuyts <j.stuyts@n200.com>
> Date: Wednesday, December 20, 2000 10:09 am
> Subject: InstantDB: Primary keys on a single column do not enforce
> uniqueness
>
> > Hi,
> >
> > I'm using InstantDB as a development database and SQL Server as a
> > deployment database. I want to create SQL-92 compliant database
> > creationscripts. I need all my single-column primary keys (the
> > usual IDs) to be
> > unique. According to the SQL spec specifiying either 'PRIMARY KEY' or
> > 'UNIQUE' enforces a uniqueness check on the column. SQL Server
> > does not
> > accept a 'CREATE TABLE' statement in which I provide both 'PRIMARY
> > KEY'and 'UNIQUE'. InstantDB however does no uniqueness check if I only
> > specify 'PRIMARY KEY'. It also allows me to specify both 'PRIMARY KEY'
> > and 'UNIQUE' and when I do it ofcourse does perform the uniqueness
> > checkthen. Who's right? Can I report this as a bug?
> >
> > (InstantDB version: 3.25, SQL Server version: 7.0)
> >
> > Johan Stuyts
> >
>
> -----------------------------------------------------------------------------
> To unsubscribe from this mailing list, send email to majordomo@enhydra.org
> with the text "unsubscribe instantdb" in the body of the email.
> If you have other questions regarding this mailing list, send email to
> the list admin at owner-instantdb@enhydra.org.
begin:vcard
n:Stuyts;Johan
tel;work:+31 (0)20 320 89 55
x-mozilla-html:FALSE
adr:;;;;;;
version:2.1
email;internet:j.stuyts@n200.com
fn:Johan Stuyts
end:vcard
|