From: Martijn Tonies
Date: January 5 2004 1:01pm
Subject: Re: Enum default values
List-Archive: http://lists.mysql.com/mysql/156828
Message-Id: <04c201c3d38c$08595420$0e02a8c0@martijn>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Hi,

> [snip]
> insert into property values ('','Book-keeper\'s Cottage','Thu');
> insert into property values ('','Inglenook Barn','Fri');
> insert into property values ('','Maggie\'s House','Fri');
> insert into property values ('','Riverside View','');
> insert into property values ('','The Manse','');
> insert into property values ('','Heathside','');
> select * from property;
>
> +-------------+-----------------------+-----------+
> | property_id | name                  | changeday |
> +-------------+-----------------------+-----------+
> |           1 | Book-keeper's Cottage | Thu       |
> |           2 | Inglenook Barn        | Fri       |
> |           3 | Maggie's House        | Fri       |
> |           4 | Riverside View        |           |
> |           5 | The Manse             |           |
> |           6 | Heathside             |           |
> +-------------+-----------------------+-----------+
> 6 rows in set (0.00 sec)
> [/snip]
>
> All expected and correct behaviour. Why? Because you're specifying a
> blank for the third value in the insert statement.
>
> insert into property values ('','Heathside','');
> insert into property values BLANK, Heathside, BLANK;

Yes, the DEFAULT doesn't apply. However, shouldn't MySQL
raise an exception because '' isn't a valid value for this ENUM
specification?

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com