Hello,
> RE:
> > And columns in primary keys must be NOT NULL. Columns in unique
> > keys can be NULL (if they are NOT NULL, then the unique key is
> > functionally the same as a primary key).
>
> OK, thanks guys for the explanation.
>
> Then the result of mysqldump table definition part:
>
> UNI
> >> I have two tables, seemigly very similar setup; the primary key is the
> >> combination of two columns. With mysqldump, however, the table
> >> definition of the two tables looks different.
> >>
> >> Mysqldump on table 1 says
> >> ...
> >> UNIQUE KEY HONstid (HONstid,HONname)
>
Hi,
RE:
> And columns in primary keys must be NOT NULL. Columns in unique
> keys can be NULL (if they are NOT NULL, then the unique key is
> functionally the same as a primary key).
OK, thanks guys for the explanation.
Then the result of mysqldump table definition part:
UNIQUE KEY HONstid (HON
At 22:27 +0100 12/28/04, Martijn Tonies wrote:
Hello,
I have two tables, seemigly very similar setup; the primary key is the
combination of two columns. With mysqldump, however, the table
definition of the two tables looks different.
Mysqldump on table 1 says
...
UNIQUE KEY HONstid (H
Hello,
> I have two tables, seemigly very similar setup; the primary key is the
> combination of two columns. With mysqldump, however, the table
> definition of the two tables looks different.
>
> Mysqldump on table 1 says
> ...
> UNIQUE KEY HONstid (HONstid,HONname)
> whereas on table 2 i
Hi,
I have two tables, seemigly very similar setup; the primary key is the
combination of two columns. With mysqldump, however, the table
definition of the two tables looks different.
Mysqldump on table 1 says
...
UNIQUE KEY HONstid (HONstid,HONname)
whereas on table 2 it says
...
