I guess that should be true of any. If the default was put there on
insert... it would be there on an update. It would only change on update if
it was specifically set to do so... I must have been in a purple haze for
missing that.

So your DB is doing what it should Rick :-)  (as long as inserts are putting
the default timestamp in)

..:.:.:.:.:.:.:.:.:.:.:.:.
Bobby Hartsfield
http://acoderslife.com

 

 


-----Original Message-----
From: Deanna Schneider [mailto:[EMAIL PROTECTED] 
Sent: Friday, February 10, 2006 8:00 AM
To: CF-Talk
Subject: Re: What's wrong with this?

I don't know mysql, but in Oracle, the default option is only relevant when
a field is created, not updated.

Also, I would try using the native function:
DateTime = CURRENT_TIMESTAMP
when you do the update. Unless your time on your CF server is set
differently than the time on the mysql server, there's no need to pass it in
as a variable.

On 2/10/06, Bobby Hartsfield <[EMAIL PROTECTED]> wrote:
>
> It definitely SHOULD be if its default has been set.
>
> ..:.:.:.:.:.:.:.:.:.:.:.:.
> Bobby Hartsfield
> http://acoderslife.com
>
>




~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:231903
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to