RE: Witango-Talk: crashing witango 5 on OS X

[Robert Shubert]

I suppose since these options aren’t possible at the moment, and it does seem that Witango is failing internally, I would turn my attention back to the search itself.   Can you not do a join? In other words, search for just the data in orders, then do a second search for the records that are joined in the second table?   Can you revert back to a standard search action and remove all the absolutely necessary columns?   Have you tried moving the search to another TAF (and use braches) or to a TCF (and use a callmethod)?   Are any of the columns holding unusual data? High-bit characters, INTs that might be null or contain spaces, anything that might return data that Witango doesn’t expect?   Is there anyway to test your site on another server or configuration? I would even be willing to setup the site in my Windows environment if we through it might help.   Robert   From: Roland Dumas [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 5:11 PM To: witango-talk@witango.com Subject: Re: Witango-Talk: crashing witango 5 on OS X     On Dec 1, 2005, at 1:20 PM, Robert Shubert wrote: Next thoughts: Can you upgrade your software to the latest versions? Mac OS DB Driver MySQL Witango   in theory, yes. This is an ecommerce site and it's the holidays. Who knows how long it would take to do the clean install of everything and get it working again.     (HINT: you can try asking WT for a 15-30 day temporary server license for 5.5, that way you can set it up side-by-side on your server and test without spending any $.) Also, can you use another method of connecting to your database, JDBC vs ODBC? I tried switching to JDBC when ODBC was crashing it. JDBC crashed it more often, so we upgraded everything to get ODBC stable and working. There was a signature for ODBC failures. It showed up in the crash log and is unmistakeable. This isn't that kinda crash. The crashed thread is witango     From a database perspective: Copy all the data into a new table Drop the existing table Recreate your table Copy all the data back will try this... Drop and recreate all indexes     how do you do that? This has only helped me solve a problem back on older versions of P.SQL, but might be worth trying. And the test best for last: Create a Stored Procedure that retrieves the records you need and just call it with a Witango DirectDBMS.   I think mysql's latest incarnation allows for stored procedures (I'm not running version 5), but I'm a little fuzzy on how you'd do that to be the equivalent of select * from orders where order_number = x Robert   ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf