RE: Cannot import mysql dump

2002-03-06 Thread Martin MOKREJŠ
> On Mon, 28 Jan 2002, Sinisa Milivojevic wrote: > > =?iso-8859-2?Q?Martin MOKREJ=A9?= writes: > > > On Mon, 28 Jan 2002, Sinisa Milivojevic wrote: Hi, I am retrying to an answer to my question from January. Could please someone from the developers have a look into this? http://lists.mysql.com

RE: Cannot import mysql dump

2002-01-28 Thread Martin MOKREJŠ
On Mon, 28 Jan 2002, Sinisa Milivojevic wrote: > =?iso-8859-2?Q?Martin_MOKREJ=A9?= writes: > > On Mon, 28 Jan 2002, Sinisa Milivojevic wrote: > > > > Hi, > > > > Hmm, well because that's just a mysqldump of a database which already > > exists in mysql and it turned out that I cannot reimport it

RE: Cannot import mysql dump

2002-01-28 Thread Sinisa Milivojevic
=?iso-8859-2?Q?Martin_MOKREJ=A9?= writes: > On Mon, 28 Jan 2002, Sinisa Milivojevic wrote: > > Hi, > > Hmm, well because that's just a mysqldump of a database which already > exists in mysql and it turned out that I cannot reimport it into mysql > back. It looks to me as a bug in mysqldump (look

RE: Cannot import mysql dump

2002-01-28 Thread Martin MOKREJŠ
On Mon, 28 Jan 2002, Sinisa Milivojevic wrote: > Are you sure that the above is the output from mysqldump ?? > > What server version ?? Look into the original posting on Jan 9 2002 for complete description. ;-) -- Martin Mokrejs - PGP5.0i key is at http://www.natur.cuni.cz/~mmokrejs MIPS / In

RE: Cannot import mysql dump

2002-01-28 Thread Roger Baklund
* Sinisa Milivojevic > Roger Baklund writes: > > I believe the problem was that this is the ouput of a > > mysqldump... why does mysqldump create invalid CREATE > > statements...? > > Are you sure that the above is the output from mysqldump ?? > > What server version ?? Of course I can not be 100

RE: Cannot import mysql dump

2002-01-28 Thread Martin MOKREJŠ
On Mon, 28 Jan 2002, Sinisa Milivojevic wrote: Hi, > This is not OK according to syntax as PRIMARY is a reserved word. > > UNIQUE KEY PRIMARY (id) > > Why don't you just say PRIMARY KEY (id) ?? Hmm, well because that's just a mysqldump of a database which already exists in mysql and it turned

RE: Cannot import mysql dump

2002-01-28 Thread Sinisa Milivojevic
Roger Baklund writes: > * Sinisa Milivojevic > > =?iso-8859-2?Q?Martin_MOKREJ=A9?= writes: > > > Hi, > > > can someone from the mysql developers tell me what i did > > wrong, if this > > > is a bug? I converted back to 3.23.42 to be on the safe side. ;) TIA > > > > > > -- > > > Martin Mokrejs -

RE: Cannot import mysql dump

2002-01-28 Thread Roger Baklund
* Sinisa Milivojevic > =?iso-8859-2?Q?Martin_MOKREJ=A9?= writes: > > Hi, > > can someone from the mysql developers tell me what i did > wrong, if this > > is a bug? I converted back to 3.23.42 to be on the safe side. ;) TIA > > > > -- > > Martin Mokrejs - PGP5.0i key is at http://www.natur.cuni.

RE: Cannot import mysql dump

2002-01-28 Thread Sinisa Milivojevic
=?iso-8859-2?Q?Martin_MOKREJ=A9?= writes: > Hi, > can someone from the mysql developers tell me what i did wrong, if this > is a bug? I converted back to 3.23.42 to be on the safe side. ;) TIA > > -- > Martin Mokrejs - PGP5.0i key is at http://www.natur.cuni.cz/~mmokrejs > MIPS / Institute for

RE: Cannot import mysql dump

2002-01-27 Thread Martin MOKREJŠ
] Cc: Martin MOKREJŠ <[EMAIL PROTECTED]> Subject: RE: Cannot import mysql dump * Martin MOKREJŠ > I have a problem to re-import sql dump from Linux 2.2.19 running > mysql Ver 11.15 Distrib 3.23.44, for pc-linux-gnu (i686) > into the same mysqld under different database. > > whil

RE: Cannot import mysql dump

2002-01-09 Thread Roger Baklund
* Martin MOKREJŠ > I have a problem to re-import sql dump from Linux 2.2.19 running > mysql Ver 11.15 Distrib 3.23.44, for pc-linux-gnu (i686) > into the same mysqld under different database. > > while running the same commandline on the source at least. > > $ mysqldump --extended-insert Bord