" <[EMAIL PROTECTED]>
Sent: Wednesday, 04 June, 2003 18:54
Subject: Re: MySQL: standard SQL compliancy: primary keys: default: should be
NOT NULL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Becoming Digital wrote:
[snip]
> from http://www.mysql.com/doc/en/CREATE_TABLE.html:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Becoming Digital wrote:
[snip]
> from http://www.mysql.com/doc/en/CREATE_TABLE.html:
> a.. A PRIMARY KEY is a unique KEY where all key columns must be
defined as NOT
> NULL. If they are not explicitly declared as NOT NULL, it will be done
> implicitly
I'm unsure what you see as a problem here? The only conflict with relational
theory would occur if MySQL *permitted* NULL values in primary keys. According
to the error message you received, MySQL is doing a fine job of preventing this.
CREATE TABLE test (
col1 INT PRIMARY KEY,
Hi Neil.
On Wed, Jun 04, 2003 at 02:33:22AM -0230, Neil Zanella wrote:
> I believe that MySQL is in error in reporting the following message just
> because I did not specify that the PRIMARY KEY should not be NULL. These
> days there are standards and SQL92, AFAIK, specifies that if the primary
>
Daniel Kasak wrote:
Neil Zanella wrote:
SQL92, AFAIK, specifies that if the primary
key is not explicitly set to NOT NULL then the RDBMS should
automatically
and silently assume the user means NOT NULL.
Sounds like the end of the world to me ;)
I suppose you have to get excited about something..
There are versions of the SQL3 document available at
http://www.inf.fu-berlin.de/lehre/SS94/einfdb/SQL3/sqlindex.html and
http://dbs.uni-leipzig.de/en/lokal/standards.pdf, free of charge.
PB
-
- Original Message -
From: Neil Zanella
To: MySQL Mailing List
Sent: Wednesday, June
Neil Zanella wrote:
Hello,
I believe that MySQL is in error in reporting the following message just
because I did not specify that the PRIMARY KEY should not be NULL. These
days there are standards and SQL92, AFAIK, specifies that if the primary
key is not explicitly set to NOT NULL then the RDBM
