Re: mysql 3.23.58

Thanks for the help.  Sorry about posting this here as i was not sure 
whether it was a bug or not.  I even emailed on [email protected] 
to ask him/her whether it was ok to post this question here but i didnt get 
a reply so i went ahead and posted it today.

Thanks for the help.
cheers

This email and any attachments may contain privileged and confidential 
information and are intended for the addressee only. If you have received 
this email in error, please notify the sender and delete this e-mail 
immediately. Any confidentiality, privilege or copyright is not waived or 
lost because this email has been sent to you in error. It is your 
responsibility to check this email and any attachments for viruses. No 
warranty is made that this material is free from any computer virus or any 
error. Any loss/damage incurred by using this material is not the sender's 
responsibility.

----- Original Message ----- 
From: "Hartmut Holzgraefe" <[email protected]>
To: "Pritesh Chandra" <[email protected]>
Cc: <[email protected]>
Sent: Thursday, August 10, 2006 11:40 AM
Subject: Re: mysql 3.23.58


Pritesh Chandra wrote:
> I have mysql 4.1.16 loaded in one server and the other server has mysql 
> 3.23.58
>
> when i do a mysqldump from 4.1.16 and try to load it on 3.23.58,
> i get this error You have an error in your SQL syntax near 'ENGINE=MyISAM 
> DEFAULT CHARSET=latin1'
>
> i cant figure out what i am doing wrong.

See http://dev.mysql.com/doc/refman/4.1/en/mysqldump.html

  --compatible=name

    Produce output that is more compatible with other database systems
    or with older MySQL servers. The value of name can be ansi, mysql323,
    mysql40, postgresql, oracle, mssql, db2, maxdb, no_key_options,
    no_table_options, or no_field_options. To use several values, separate
    them by commas. These values have the same meaning as the corresponding
    options for setting the server SQL mode. See Section 5.2.5,
    “The Server SQL Mode”.

    This option does not guarantee compatibility with other servers.
    It only enables those SQL mode values that are currently available for
    making dump output more compatible. For example, --compatible=oracle
    does not map data types to Oracle types or use Oracle comment syntax.

    This option requires a server version of 4.1.0 or higher.
    With older servers, it does nothing.


PS: the bugs list is not the right list for questions like this,
     better use

        http://lists.mysql.com/mysql

     or one of the forums at

        http://forums.mysql.com/

     next time


-- 
Hartmut Holzgraefe, Senior Support Engineer                            .
MySQL AB, www.mysql.com




-- 
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe:    http://lists.mysql.com/[email protected]