Hello Guest, please login or register.
Did you miss your activation email?
Login with username, password and session length.

Pages: [1]   Go Down

Author Topic: Help! Can you stop TimeStamp during update?  (Read 943 times)

0 Members and 1 Guest are viewing this topic.
Help! Can you stop TimeStamp during update?
« on: February 25, 2007, 08:51:08 am »
  • *
  • Reputation: +0/-0
  • Offline Offline
  • Gender: Male
  • Posts: 563
When Updating a record is there any way to stop a timestamp field from changing, I want it to keep the time from the creation not each update...

Thanks.
« Last Edit: March 25, 2007, 11:11:38 am by Benito »
Logged

I ♥ Open Girlfriend (What!? I didn't add this.. must have been Solly!)
  • My DevArt Account
Re: Help! Can you stop TimeStamp during update? ...
« Reply #1 on: February 25, 2007, 01:35:15 pm »
  • IBV
  • *
  • Reputation: +0/-0
  • Offline Offline
  • Gender: Female
  • Posts: 1075
Quote from: Benito on February 25, 2007, 08:51:08 am
When Updating a record is there any way to stop a timestamp field from changing, I want it to keep the time from the creation not each update...

Thanks.

You probably have to remove the "ON UPDATE CURRENT_TIMESTAMP" attribute for the field (the same place where you can put "UNSIGNED" and "UNSIGNED ZEROFILL" etc. It could also be that you have accidentally put in an update for the field in your SQL statement (it often happens when you copy statements that are almost the same but forget to actually make it correct.
Logged
My signature is empty.
Re: Help! Can you stop TimeStamp during update? ...
« Reply #2 on: February 25, 2007, 04:37:14 pm »
  • *
  • Reputation: +0/-0
  • Offline Offline
  • Gender: Male
  • Posts: 563
Ah thanks, I'd imagine its just because I set up new MySQL databases from memory of the old ones :P.
Logged

I ♥ Open Girlfriend (What!? I didn't add this.. must have been Solly!)
  • My DevArt Account
Pages: [1]   Go Up
« previous next »

 


Contact Us | Legal | Advertise Here
2013 © ZFGC, All Rights Reserved


Page created in 0.043 seconds with 40 queries.