Yes? Why are you surprised? A DATE field is *not* a string, even though you are allowed to initialize it with (or compare it to) a specially formatted string.
You can also initialize or compare DATE fields with numbers, so you could have done
proj_end_date = 0,
But the most sensible thing to do, if you want to purposely *NOT* specifiy a given value, is exactly what you would do with any other field type:
proj_end_date = NULL,
NULL is a special keyword that is reserved for just this kind of purpose.
Anyway, if you choose to use 0 instead of NULL, then you should probably be consistent and use numbers for your other dates, thus:
UPDATE transprojinfo SET projname = 'Blue Book - Live Nation',
projdescription = 'Scraping the event page of given websites',
proj_initiator = '148',
proj_initiate_date = 20080915,
proj_received_date = 20080915,
proj_status = 'In Progress',
division = 'E Commerce',
proj_end_date = 0,
proj_comments = 'asdfasdf' WHERE projid = '15'
I do *NOT* recommend this. I think NULL is the better choice. But up to you.
p.s.: Why do you use
WHERE projid = '15'
instead of
WHERE projid = 15
???
Surely a field named projid is a number field, not a text field. No?
|
