On Dec 1, 2005, at 3:24 PM, Phil Wade wrote:
I hope this explains the situation on why we are unable to decode
backtraces for Witango Server 5.0 on OS X more clearly and why
debugging your 5.0 problem is going to be trial and error and may
not be able to be solved without upgrading the OS, ODBC, DB and
Witango Server.
cutting to the chase:
I accept that there isn't a system available to customer support to
trace out a problem in a previous version of the server and that I'm
in a trial and error situation. Also, I know that the problem might
be a bug in one of the systems that would be replaced by better
systems were I to upgrade everything. Upgrading everything to solve a
bug is a non-trivial thing to do in terms of time, cost, etc., and it
might not cure the problem if it's in the class of !CST corruption
errors introduced by the studio.
That's why I'm looking for ideas to try that I haven't tried yet.
For something this odd to be going on with a relatively simple action
is perplexing. It was not triggered by the OS or ODBC upgrade, but by
the simple addition of a field in a table. For a simple query to nuke
a server only when a record is hit the first time and then only
randomly, suggests that something might be funky in the database and
it's passing back something that gives witango indigestion when mysql
is updating its internal index. All that stuff is beyond me.
Looking for ideas that are possible to try short of shutting down the
business for clean installs during the busiest season of the year.
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
