I'm putting this back on the list where it belongs; that enables everyone to
benefit from the discussion, both now and in the future via the archives.
--
Sorry, you're right, I didn't read your entire question thoroughly. You set
the default value for a DATETIME column (or any other type for t
#x27;$
> state2','$agency','$bmothername','$mage','$monthmdob','$daymdob','$yearm
> dob','$bfathername','$fage','$monthfdob','$dayfdob','$yearfdob','$commen
> ts'
27;$fage','$monthfdob','$dayfdob','$yearfdob','$commen
ts','$signupdate')";
$signupdate is the one that I wanted to be the timestamp obviously!!!
LOL
Thanks in advance for any help someone can give me
-Original Message-
From: Rober
At 12:18 -0800 2001/12/14, Steve Osborne wrote:
> Timestamp additional info:
>
> INSERT INTO Owners (NameID,ProductsKey,RegNum,ProdRegDate)
>VALUES ('$NameID','1','$RegNumc','NULL');
>
>ProdRegDate is the field that I want to timestamp. (Again, I've tried
> passing '', NULL, and 'NULL').
>
> St
You have not shown us what you are doing, only described it.
Write a test case that creates a table with a timestamp field, populates the
table, and does a select on it. Show us what you are doing, and the
results.
Steve Osborne wrote:
> I've tried passing nothing '' and NULL and 'NULL', and s
mysql (filter)
Timestamp additional info:
INSERT INTO Owners (NameID,ProductsKey,RegNum,ProdRegDate)
VALUES ('$NameID','1','$RegNumc','NULL');
ProdRegDate is the field that I want to timestamp. (Again, I've tried
passing '', NULL, and 'NULL').
Steve
-
I've tried passing nothing '' and NULL and 'NULL', and still the zero's. In
response to Mikel, the field is declared as NULL and default is NULL. I've
experimented with changing the Null and Default columns in phpMyAdmin, but
it stays as NULL and default as NULL.
Steve.
>
> Steve Osborne wrot
Steve Osborne wrote:
>
> Rick,
>
>
> Just add a field of type TIMESTAMP to your record. Whenever the field is
> added or updated, this field will be updated as well.
>
>
> The field is already a 'timestamp(14)' type field, but all that is being
> stored in the fields are zero's
Rick,
Just add a field of type TIMESTAMP to your record. Whenever the field is
added or updated, this field will be updated as well.
The field is already a 'timestamp(14)' type field, but all that is being
stored in the fields are zero's.
Do you know what could be causing this?
Hi,
I have just checked the logs, and the point is that in the update log
there are statements for setting the timestamp, and in the binary log
not.
Is this OK?
Thanks again.
Gabriel
> -Original Message-
> From: Gabriel Corneanu
> Sent: Monday, April 30, 2001 11:23 AM
> To:
10 matches
Mail list logo