RE: [PHP-DB] Insert, Arrays, Null

2002-04-05 Thread Rick Emery
When you say ...account for either a numeric or NULL value ..., do you mean SELECT a value that could be NULL? If so, the query is SELECT * FROM mytable WHERE cusa IS NULL || cusa = 0 -Original Message- From: Zach Curtis [mailto:[EMAIL PROTECTED]] Sent: Friday, April 05, 2002 9:11 AM

RE: [PHP-DB] Insert, Arrays, Null

2002-04-05 Thread Zach Curtis
- From: Rick Emery [mailto:[EMAIL PROTECTED]] Sent: Friday, April 05, 2002 8:18 AM To: 'Zach Curtis'; [EMAIL PROTECTED] Subject: RE: [PHP-DB] Insert, Arrays, Null When you say ...account for either a numeric or NULL value ..., do you mean SELECT a value that could be NULL? If so, the query

RE: [PHP-DB] Insert, Arrays, Null

2002-04-05 Thread Rick Emery
; [EMAIL PROTECTED] Subject: RE: [PHP-DB] Insert, Arrays, Null The data being read dynamically into the array could contain values which are NULL (the default) or numeric (if a numeric value exits). However, the query is using a INSERT INTO and I can't seem to form this query to account

RE: [PHP-DB] Insert, Arrays, Null

2002-04-05 Thread Zach Curtis
. Is there an advantage to using the VALUES clause? Thank you for your assistance. Zach -Original Message- From: Rick Emery [mailto:[EMAIL PROTECTED]] Sent: Friday, April 05, 2002 8:42 AM To: 'Zach Curtis'; [EMAIL PROTECTED] Subject: RE: [PHP-DB] Insert, Arrays, Null Is there some reason you

RE: [PHP-DB] Insert, Arrays, Null

2002-04-05 Thread Rick Emery
Using VALUES() is faster Nothing really wrong with SET clause, though -Original Message- From: Zach Curtis [mailto:[EMAIL PROTECTED]] Sent: Friday, April 05, 2002 10:34 AM To: Rick Emery; [EMAIL PROTECTED] Subject: RE: [PHP-DB] Insert, Arrays, Null Terrific! I tried an example