I have been using Witango Dev Studio v5.5 for OS X for quite some
time, with 5.0 server, and now 5.5.009 server, never seen this
behavior, deploying to windows.
Hopefully, I hear from support, and I will run some tests this
weekend, on Primebase, and MS SQL.
--
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 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 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.
--
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 Jul 14, 2005, at 6:42 AM, Roland Dumas wrote:
I was just fiddling with such a case yesterday and have had the
problem on and off for quite a while.
I insert a timestamp and nothing gets to the db. I edit the
timestamp to include a format=datetime: xxxx and it works. If I
edit that action again, it may stop working and then reverting to
the plain timestamp format works.
been that way for a while
On Jul 13, 2005, at 11:00 PM, Robert Garcia wrote:
I am helping another witango user(Mark Weiss), with a setup of OS
X 10.3.9 server with 5.5.009, Openlink iODBC 3.52.1 connecting to
Primebase 4.2.49 also running on OS X.
The issue has to do with errors inserting timestamps. I made a
test with my setup, which is identical, 5.5.009, and Primebase
4.2.49, but I am using Windows, not OS X.
I have checked the setup of his database server, and the witango
server, and they are setup the same as mine, but look at debug
when he inserts a timestamp:
____________________________________________________________________
____
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
<pastedGraphic.png>
Normally, I would see the timestamp escaped, like this below, a
test from my system:
<pastedGraphic.png>
I VERIFIED that both test were inserted with action like so:
<pastedGraphic.png>
So, why is witango escaping on mine, and not his system? Does
witango escape when certain conditions apply with ODBC? What are
those conditions, so I can check with Primebase? When I use other
tools, I do not see issues with ts inserts, and I have verified
that both ODBC/DB systems on both machines are expecting date in
YYYY-MM-DD HH:MM:SS, standard SQLTimeStamp format.
I have verified that on the OS X system, mark did not alter the
DB so that it looks for a different format.
Hoping Support, or someone on the list may have some insight.
--
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/
--
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
