Okay..?
Your explanation makes sense, but it seems a bit counter-intuitive. In my
mind, if you insert identical values (no matter what they are) into a
field that is declared to be a unique key, the database should complain
like crazy, if not completely disallow the action.
In any case, thank
ND SQL TEST OUTPUT
>Fix:
No idea.
>Submitter-Id:
>Originator:Matt Loschert
>Organization: ServInt Internet Services
Matt Loschert | email: [EMAIL PROTECTED]|
Software Engineer | web: http:
On Thu, 22 Feb 2001, Sinisa Milivojevic wrote:
> Matt Loschert writes:
> > On Thu, 22 Feb 2001, Sinisa Milivojevic wrote:
> >
> > > [EMAIL PROTECTED] writes:
> > > > >Description:
> > > >
> > > > As of mysql
,
> > KEY User(User) < pukes on this line
> > ) TYPE=MyISAM COMMENT='Database privileges';
> >
> >If a space is added (as in: "KEY User (User)"), the file will import correctly.
< pukes on this line
) TYPE=MyISAM COMMENT='Database privileges';
If a space is added (as in: "KEY User (User)"), the file will import correctly.
I looked through the source file mysqldump.c and it appears that there always
should be a sp
