Hello,
I'm using mysql-max 3.23.49 binary distribution.
I use mysqldump utility to dump tables from my DB.
for example:
mysqldump --opt -u root -p EFDB users users.sql
users.sql file contains:
--
-- MySQL dump 8.21
--
-- Host: localhostDatabase:
It would seem that there is a bug, and it's that create table
accepts an 'illegal' definition. It should either convert the integer
to a literal (making the definition legal and dumpable), or it should
barf on it.
IMO, of course.
--Pete
[Charset iso-8859-1 unsupported, filtering to ASCII...]
mysqldump regenerates a bad sql statement from a bad initial create table.
When you create this table for example (ok it's not a really nice definition):
CREATE TABLE TESTBADDUMP (
e_test enum('0','1') NOT NULL default 0
);
desc TESTBADDUMP;
[EMAIL PROTECTED] writes:
mysqldump regenerates a bad sql statement from a bad initial create table.
When you create this table for example (ok it's not a really nice definition):
CREATE TABLE TESTBADDUMP (
e_test enum('0','1') NOT NULL default 0
);
desc
Hi,
mysqldump regenerates a bad sql statement from a bad initial create table.
When you create this table for example (ok it's not a really nice definition):
CREATE TABLE TESTBADDUMP (
e_test enum('0','1') NOT NULL default 0
);
desc TESTBADDUMP;
Try quoting (' ') the 0 in your create:
CREATE TABLE TESTBADDUMP (
e_test enum('0','1') NOT NULL default '0' );
-^
You should then get the result you want.
Have a great day...
John
On Monday 18 June 2001 08:54, [EMAIL PROTECTED] wrote:
mysqldump
Le Mon, Jun 18, 2001 at 04:04:52PM +0300, Sinisa Milivojevic a écrit:
[EMAIL PROTECTED] writes:
mysqldump regenerates a bad sql statement from a bad initial create table.
When you create this table for example (ok it's not a really nice definition):
CREATE TABLE TESTBADDUMP (
an invalid statement.
thanks,
-- Andrew
- Original Message -
From: Thomas Karcher [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, June 18, 2001 9:08 AM
Subject: Re: mysqldump bug during regenerate enum field.
Hi,
mysqldump regenerates a bad sql statement from a bad initial create
Guillaume Fougnies writes:
ok so it's a failure from mysqldump.
I know this declaration is not really correct but mysqldump must regenerate a
correct sql statement (good when pipe in mysql client i mean at least ;) ).
It's not the case.
Regards,
--
Guillaume FOUGNIES
Research
Sinisa,
A good way to prove that mysqldump is doing what it should, might be to do a
describe TESTBADDUMP;
I think this will prove that mysqldump is just dumping what is in the table
def, which is all you can expect.
Have a great day...
John
On Monday 18 June 2001 09:46, Sinisa Milivojevic
Hi all,
I don't know if this is a bug in mysqldump but it
behaves in a strange way. I tried to use mysqldump to
dump out the data and structure of a small database in
order to populate another database but not all records
are dumped. I tried to flush the tables from mysql
server using FLUSH
11 matches
Mail list logo
