List:General Discussion« Previous MessageNext Message »
From:Michael Dykman Date:July 14 2009 1:30am
Subject:Re: show warnings;
View as plain text  
It is a little bit of paranoia which is not unhealthy.  You might be
running those scripts on a dev server or a shared host where the
default warnings setting is not the default nor is it necessarily
under your control.  You are right, warnings *should* be enabled by
default, but when you want to be guaranteed of consistent behaviour,
explicitly ask for what you want.

 - michael dykman

On Mon, Jul 13, 2009 at 8:20 PM, Artie Ziff<artie.ziff@stripped> wrote:
> Hello,
> I am returning to mysql after long break, so not experienced with
> details. I inherited a text file with the mysql DDL statements which
> create database and tables, etc. Each 'create' or 'drop' table statement
> is preceded with a 'show warnings' statement. Since this file is used to
> initialize a new database in mysql server, is there any reason to have
> warnings enabled like this? It seems the warning would be generated 100%
> of the time since the database did not exist before. So, my question is,
> is there some good reason to include 'show warnings' statements into a
> file that is intended to initialize a database that did not exist
> before? It seems unnecessary however perhaps there is some situation
> where this makes sense.
> Cheers,
> AZ
> --
> MySQL General Mailing List
> For list archives:
> To unsubscribe:

 - michael dykman
 - mdykman@stripped

 - All models are wrong.  Some models are useful.
show warnings;Artie Ziff14 Jul
  • Re: show warnings;Michael Dykman14 Jul
  • Re: show warnings;fire914 Jul
  • RE: show warnings;Jerry Schwartz14 Jul