ot; in NOT NULL column.
Babs
-Ursprüngliche Nachricht-
Von: Michael Stassen [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 14. April 2004 18:21
An: Ruslan U. Zakirov
Cc: Keith C. Ivey; [EMAIL PROTECTED]; B. Fongo
Betreff: Re: NOT NULL column behaves strangely
Ruslan U. Zakirov wrote:
Ruslan U. Zakirov wrote:
Keith C. Ivey wrote:
On 14 Apr 2004 at 17:27, B. Fongo wrote:
I expected a warning because of the Token column shouldn't be NULL!
It's not NULL. It's the empty string, which is the default value,
since you didn't give it a specific default value. See the "CREATE
TAB
004 17:39
An: B. Fongo; [EMAIL PROTECTED] Mysql. Com
Betreff: Re: NOT NULL column behaves strangely
Hi,
> Why does MySQL accept this insert statement with a warning?
>
> Insert into Sessions (id) values (20de8376640263673ea03938);
>
> Query OK, 1 row affected.
>
> I expected a
Keith C. Ivey wrote:
On 14 Apr 2004 at 17:27, B. Fongo wrote:
I expected a warning because of the Token column shouldn't be NULL!
It's not NULL. It's the empty string, which is the default value,
since you didn't give it a specific default value. See the "CREATE
TABLE" documentation:
Hi,
> Why does MySQL accept this insert statement with a warning?
>
> Insert into Sessions (id) values (20de8376640263673ea03938);
>
> Query OK, 1 row affected.
>
> I expected a warning because of the Token column shouldn't be NULL!
>
> I have a table with three columns:
>
> Id # int not null
> T
On 14 Apr 2004 at 17:27, B. Fongo wrote:
> I expected a warning because of the Token column shouldn't be NULL!
It's not NULL. It's the empty string, which is the default value,
since you didn't give it a specific default value. See the "CREATE
TABLE" documentation:
If no DEFAULT value i
Why does MySQL accept this insert statement with a warning?
Insert into Sessions (id) values (20de8376640263673ea03938);
Query OK, 1 row affected.
I expected a warning because of the Token column shouldn't be NULL!
I have a table with three columns:
Id # int not null
Token # char (1) not
