I use Myself <<- mean MySQL :-)
----- Original Message -----
From: [EMAIL PROTECTED]
To: [email protected]
Sent: Tuesday, October 02, 2007 3:19 AM
Subject: Time to say good bye to Witango --> was Re: Witango-Talk: Killing a
database connection
I use Myself for huge databases and MS ACCESS for quick and dirty projects.
Never have had problems with Witango.
But, also I change to PHP, the reason is: here I have more add ons and it
work on big projects. And at least: It is for free.
For non-programmers PHP sucks, but for professional programmers, PHP work
fine. Same as Witango. If You don't know how a database work, so you have
problems using Witango. On beginning with TANGO on MacOS, it was fine to have a
Tool what have make for you all the html-Code what you have needed. But for
today, I miss XML-Codes, I miss add. functions (like a simple calendar/Dating
function; like a BBS; like a simple fotogalery [postings, readings]; I miss
AJAX; JAVA compilations (for free) a.s.o).
In my eyes, TANGO was all-time the first choice (in the past) for Web-Devs.
But the selling from Everyware to Pervasive and
after to With for less as xx.xxx US$ have killed the application. With (Phil
and Sophie) have make a great job with Witango 5 - no discussion. [They have
only buy it, because it was cheaper as make a new development to his own
customer].
But sorry, I think to spending more money into developers (and
Reseller/Distributors) as in a new flat with a tennis play place and a pool and
to work really on a new Witango version had can be the right way to make a very
good products. The time of "garage"-developments with one person (Phil) is over.
Time to say good bye to Witango and to all of the group.
regards or in german:
Mit freundlichen Grüßen,
Daniel Richardy
Formerly Witango Distributor for Germany, Austria, Switzerland (in one Word:
Europe).
______________________________________________________________________
SoftDes GmbH, Software, EDV-Beratung, Grafik-Design
Auwaldstrasse 104 - D 79110 Freiburg - Tel: +49 - 761 - 4 555 666
Geschäftsführer: Daniel Richardy; Sitz und Registergericht: Freiburg - HRB
6109
Web: www.softdes.de Mail: [EMAIL PROTECTED]
----- Original Message -----
From: Robert Garcia
To: [email protected]
Sent: Tuesday, October 02, 2007 1:23 AM
Subject: Re: Witango-Talk: Killing a database connection
No, I agree. Witango is very particular. But in my experience, you aren't
going to get much help on the witango side with that, so you are better off
changing to mysql or mssql, or leaving witango.
The number of issues that have been brought up with oracle in the past are
very long. I am actually working with 2 companies that had oracle. I already
converted one over to mysql, and the second one in the process. The second one,
tried JDBC for oracle first, which was better, but mysql is about the most
trouble free database to use with witango.
I use PHP on my biggest projects, and have a couple of installations on
oracle and I don't see the same issues that witango has.
As a side note, I originally moved to mysql, just to have a more trouble
free witango setup, which it DEFINITELY did. However, I became a huge mysql
advocate, and am in love with its power and flexibility.
Just food for thought. But to sum up, MANY on this list have come up
against issues with oracle and witango, and there has been little to no
resolution.
--
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 Oct 1, 2007, at 3:35 PM, Shannon Henderson wrote:
We use JDBC with Filemaker and OCI with Oracle. We're not having trouble
with anything but Witango connections now. I'm finding it harder to believe
that all of the driver creators got it wrong and Witango got it right...
On Oct 1, 2007, at 2:43 PM, Robert Garcia wrote:
The old database I used to use, would require this when for some reason
witango would burp or lost connection. It was very frustrating, but I never
found a way to just stop that one thread from the witango side. It should be
noted, that other dbs don't require this. Both MS SQL 2000 and MySQL don't have
this problem. I can reboot mysql, and leave witango alone, and it will
reconnect. This led me to realize, it is more of an issue with the ODBC
driver/db from the vendor. I experimented with other code and found this to be
the case, outside of witango.
What database do you use?
--
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 Oct 1, 2007, at 1:20 PM, Shannon Henderson wrote:
Does anyone know if it is possible to kill open database connections
without restarting the witango server process? We've had some cases lately
where a connection will fail somewhere between the witango server and the
database server. Everything but witango recognizes that the session is dead
and ditches it. Rather than starting a new session, witango just keeps
returning "113 Unable to communicate with the specified data source. The
existing connection was lost." on the old session until the datasource timeout
kicks in.
The problem is that the some other sessions are often fine, so I hate
to kill off everything if I can tell that there are specific dead sessions.
--------------------------------------------------------------------
Shannon Henderson
Web Support Services
Reed College
Portland, OR 97202-8199
[EMAIL PROTECTED]
--------------------------------------------------------------------
________________________________________________________________________
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
________________________________________________________________________
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
