;-(
14 hours later....
Database returned "An unknown error". At least SyBrowser didn't crash ;-)
A simple .connect worked immediately and I was on and going
At 8:45 AM +1100 27/3/03, Dr Gerard Hammond wrote:
Dave,
Well it is about 6.45pm here now and I am going home. I have opened
a MySQL connection via SyBrowser (http://www.macsos.com.au). When I
come back in to work tomorrow I'll let you know if I can get data
back to the client without reconnecting.
Hi all,
I'm pretty sure I've been bit bas by this bug on my current project
(my first using RB as a front end for MySQL). For me its been a
particularly frustrating bug since the crash occurs lower than the
IDE when debugging, but application crashlogs reliably show the
crash occuring at the point where database connection occurs.
I've believe I've created a sustainable workaround by handling and
maintaining the database connection at the app object level, as I
have seen advocated here on the list, but have the following
question for anyone with more RB / MySQL experience than me:
if I maintain an open connection to a MySQL database persistently
within the app, what is a reasonable timeout to use when deciding
to refresh the connection? My current implementation uses 5 minutes
of connection inactivity as the trigger for database re-connection
(that is, if no activity on the connection has occurred in 5 or
more minutes, on a new database access event, the connection is
re-established). Is 5 minutes too long, or am I jumping the gun,
and the timeout can be increased?
Any feedback or advice is much appreciated.
Thanks,
--
Cheers,
Dr Gerard Hammond
Bioinformatic Analyst
Garvan Institute of Medical Research, Sydney, Australia.
What do you call a fish with no eyes? A fsh.
---
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>
.
|