Harald Fuchs wrote:
You _did_ enter some data, namely a string which just happens to be
the empty string (which in turn is different from no data, i.e. NULL).
How should MySQL know that you don't want empty strings?
I think the user expects:
INSERT INTO table (bar) VALUES (text);
to behave
: Wednesday, January 15, 2003 1:23 AM
To: [EMAIL PROTECTED]
Subject: Re: InnoDB table, NOT NULL question
In article [EMAIL PROTECTED],
Adolfo Bello [EMAIL PROTECTED] writes:
This is wierd. If you define a field as not null is because you want
the user to enter some data, for example, First Name
On Monday 13 January 2003 23:38, Gabe Geisendorfer wrote:
Hello, I'm in the process of moving from Postgres to MySQL and I have a
question.
+How do you prevent a field from being left empty?
I have an InnoDB table that looks like the following.
CREATE TABLE `stuff` (
`stuff_id`
Hello, I'm in the process of moving from Postgres to MySQL and I have a
question.
+How do you prevent a field from being left empty?
I have an InnoDB table that looks like the following.
CREATE TABLE `stuff` (
`stuff_id` int(11) NOT NULL auto_increment,
`somevalue1` varchar(35) NOT NULL,
.
Thanks,
Gabe
-Original Message-
From: Egor Egorov [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 14, 2003 7:11 AM
To: [EMAIL PROTECTED]
Subject: re: InnoDB table, NOT NULL question
On Monday 13 January 2003 23:38, Gabe Geisendorfer wrote:
Hello, I'm in the process of moving from
]
Subject: Re: InnoDB table, NOT NULL question
Hello, I'm in the process of moving from Postgres to MySQL and I have
a question.
+How do you prevent a field from being left empty?
I have an InnoDB table that looks like the following.
CREATE TABLE `stuff` (
`stuff_id` int(11) NOT NULL
I have an InnoDB table that looks like the following.
CREATE TABLE `stuff` (
`stuff_id` int(11) NOT NULL auto_increment,
`somevalue1` varchar(35) NOT NULL,
`somevalue2` varchar(35) NOT NULL,
PRIMARY KEY (`stuff_id`)
) TYPE=InnoDB COMMENT='stuff table';
I run the following