Hi.
On Wed 2003-01-22 at 23:07:24 -0800, [EMAIL PROTECTED] wrote:
> I'm really just currious as to WHAT you would want to see as opposed
> to NULL?
Well, you asking the wrong guy, because I did not need that feature,
but I'll try to explain anyhow.
They want to see an error instead. It is the
I'm really just currious as to WHAT you would want to see as opposed
to NULL?
How could you have a field that has no value? What would it mean?
NULL is the answer to this. It is recording the absence of
something. So, I would say that this is an expected behaviour of any
database engine.
On Wednesday 15 January 2003 22:36, Gabe Geisendorfer wrote:
> Thanks, I check it out.. Any idea if this 'deficiency' is scheduled to
> change?
Yes.
http://www.mysql.com/doc/en/TODO_future.html
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This
Thanks, I check it out.. Any idea if this 'deficiency' is scheduled to
change?
Thanks,
Gabe
-Original Message-
From: Benjamin Pflugmann [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 15, 2003 9:49 AM
To: Gabe Geisendorfer
Cc: [EMAIL PROTECTED]
Subject: Re: NOT NUL
Hello.
On Tue 2003-01-14 at 09:32:02 -0800, [EMAIL PROTECTED] wrote:
> I'm aware that NULL and "" are not the same thing.. I would like to
> prevent the column from accepting values automatically ( with out the
> presence of a DEFAULT).
[...]
The problem is: You have a DEFAULT, you just don't kno
Sent: 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 d
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 beha
> >>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';
> >>
1 AM
To: [EMAIL PROTECTED]
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
x27;s.
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 o
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,
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_i
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,
13 matches
Mail list logo
