On 31-03-2003 03:22, "Dave Slack" <nospam at forestdigital dot com> wrote:
> The design you used for your site was also my original approach in the
> project I'm working on: I had a class that handled all the database
> functionality of the app, and when my app needed data, I'd instantiate
> an object from the class, hand it its connection data, and then call a
> class method that would return the data I wanted. The database access
> class would create an instance of a MySQLDatabase, connect to it, and,
> on a successful connection, handle the SQL transaction, parse the data
> returned as needed and return the data or an error as appropriate.
Mind you, I do not create a new instance of my MySQL-class on every SQL
request. I create only one, global, instance, hand that the connection data,
and connect on every read or write action.
This seemed to work fine, but further testing confirms your problem: after
about 230 connections have been made, the program freezes, in wait for
another connection that never gets there...
:-(
---
A searchable archive of this list is available at:
<http://support.realsoftware.com/listarchives/search.php>
Unsubscribe:
<mailto:realbasic-nug-off at lists dot realsoftware dot com>
Subscribe to the digest:
<mailto:realbasic-nug-digest at lists dot realsoftware dot com>
.
|