Posted by Steve Dassin on 07/15/07 22:03

"Erland Sommarskog" <esquel@sommarskog.se> wrote in message
news:Xns996ECA8E4FCA0Yazorman@127.0.0.1...
> .
> There are more possibilities to maintain data integrity than relational
> databases. But
> it is a complex matter, and relational databases has proven to do a
> decent job of it.
>.

The idea of 'integrity' in sql is immature. Unfortunately most here are only
familiar with
what is served up as 'integrity' in bol. Imagine if sql was as 'dedicated'
to integrity as
it is to performance. What sort of 'integrity' features would it have? Could
you call
it more than 'decent'? Let sql do what it does best - access data. Using sql
to define
a schema is using it at what it does not do best. Such a simple concept -:)

www.beyondsql.blogspot.com'

• Next in forum: Re: Relationships error, C# Visual Studio 2005 database bug?, "the columns in table XYZ do not match an existing primary key or UNIQUE constraint", copying columns
• Prev in forum: Re: Relationships error, C# Visual Studio 2005 database bug?, "the columns in table XYZ do not match an existing primary key or UNIQUE constraint", copying columns
• Thread view: Re: Relationships error, C# Visual Studio 2005 database bug?, "the columns in table XYZ do not match an existing primary key or UNIQUE constraint", copying columns

[Reply to this message]