Re: Witango-Talk: Mac OS X Timestamp issue.

[Roland Dumas]

I've been thinking it should, but haven't had the discipline to capture the before/after and works/not works. For me, it's just a case of editing the content of a field being written to and then finding that the timestamp broke. Since this is a rare event, I don't think to capture the XML before I opened  up that action. It's more like, "Oh s***, that one again!" On Jul 14, 2005, at 8:47 AM, Mark Weiss wrote: How great to have a confirmation of this distressing behavior. I thought I was going nuts. I am wondering though, if the editor is screwed up, wouldn’t it show up in the xml somehow? Mark On 7/14/05 8:30 AM, "Roland Dumas" <[EMAIL PROTECTED]> wrote: On Jul 14, 2005, at 6:59 AM, Robert Garcia wrote: Exactly, but you should not have to edit the timestamp with a format. as in my case, it should escape the timestamp on insert and update. And Mark, has seen the problem not consistent either. What database are you using? I m using mysql, witango 5, dev studio 5.5 I am suspecting it is a bug in Witango OS X. I am thinking of setting up a test environment, and try to reproduce with more than one dbms, and try with JDBC. And see what the results are, but I would like to here from witango support first. I suspect the dev studio. In my experience - by trial and error - if an action is working, it will keep working until you edit something in it. Then it will consistently not work until you edit in the format:datetime. Then it will consistently work until on some random edit of the action (not every time) it stops working, whereupon to get it working, you have to take out the format:datetime. To me, that indicates the dev studio is doing something.  ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf