That sounds reasonable to me, but better let more experienced hands,
particularly in db design, chime in here...
There are some good reasons to allow Null, so perhaps it would be wise to
consider some other ideas before plunging forward. :)
Just my 0.02
-m-
-Original Message-
From: R
I ran into the issue where data had been written, and then a Null was
written.
The presence of Null in a field may not in fact guarantee that data has
never been written.
-m-
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, September 15, 2003 11:12
To:
Null is a special value and cannot be tested in the same manner as a string
or other value. Yes, there is a difference. If the column is Null, a
comparison operation such as a.field == "" or a.field == "something" will
both return Null.
Maybe this document will help:
A.5.3 Problems with NULL V
esday, September 09, 2003 12:35
To: Mark Richards; [EMAIL PROTECTED]
Subject: RE: How to get previous and next result
Hi there!
--- Mark Richards <[EMAIL PROTECTED]> wrote:
> If you simply have a table with an id field that has
> the auto-increment
> attribute (field is int(10))
terms often, not like a SQL designer!
Hugs,
Mark Richards
-Original Message-
From: Maria Garcia Suarez [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 09, 2003 11:53
To: [EMAIL PROTECTED]
Subject: How to get previous and next result
Hi there!
I'm currently developing a web where w
Grant,
>From my old relational database days we'd create a table of courses and
index this so it could be linked from your semester table. This way, you'd
have a single entry for each course. Should the course change, the
maintenance nightmare is alleviated by only having to change the course
en
Yes, that advice worked perfectly. Now I understand.
This is one very nice data storage system. It's fast, and it can deal with
multiple pointers - separate sessions - into the same table without
conflict. I guess it's up to the programmer to make certain that one
connection doesn't change da
id =
'".$recid."';";
$result2 = mysql_query($q2)
}
Is this a valid use of MySQL? I am concerned that executing the update
query might somehow effect the first one that is used in the outer loop.
Mark Richards
--
MySQL General Mailing List
For list archives: htt
id =
'".$recid."';";
$result2 = mysql_query($q2)
}
Is this a valid use of MySQL? I am concerned that executing the update
query might somehow effect the first one that is used in the outer loop.
Mark Richards
--
MySQL General Mailing List
For list archives: htt
id =
'".$recid."';";
$result2 = mysql_query($q2)
}
Is this a valid use of MySQL? I am concerned that executing the update
query might somehow effect the first one that is used in the outer loop.
Mark Richards
--
MySQL General Mailing List
For list archives: htt
10 matches
Mail list logo
