I have never used 4. Many moons ago, we had some code, that specified
the format, because we were having issues because of !CST, and didn't
know what was causing it. We have changed all back to
<@currenttimestamp>, since we are not having CST issues anymore, we
found some places that were left. But that does match the format.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
On Apr 13, 2007, at 5:39 PM, William M Conlon wrote:
MySQL TIMESTAMP and DATETIME format changed from 3.23 to 4. I'm
pretty sure the format you used isn't the new format.
Bill
On Apr 13, 2007, at 3:19 PM, Robert Garcia wrote:
We are using the latest 55 server, and we are seeing on occasion,
dates like this:
2000-11-00 00:00:00
When this was used on insert:
<@CURRENTTIMESTAMP FORMAT="%Y-%m-%d %H:%M:%S">
It doesn't happen often, but it is happening. Has anyone else seen
this?
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
_____________________________________________________________________
___
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
