On 2001.08.23, Mark Hubbard <[EMAIL PROTECTED]> wrote:
> There are 6 bytes in the log file. It reads 13029. That's all. Weird.
Is that the log file, or the pid file? That looks like a pid to
me.
> I put the $datasource back in to ns_db gethandle. Didn't work. Then I
> realized $datasource is supposed to be a pool name, not an actual datasource
> name (ns_db docs). So I changed where the form had markhpc to read mypool
> (thats my pool name) and voila! 23 rows affected! Thank you Dossy!
Oh, duh, right. I'm an idiot -- I said you'd gotten that part
right. Heh.
> Wow that was easy. It's just a matter of the right kind of hand-holding
> and/or docs to get the various pieces in place and working. I tell you, an
> RPM containing all these pieces already configured would be very good for
> spreading AOLsvr into the formerly-Windows world.
Or, as I keep thinking I'll find the time, a web-based installation
wizard that runs within AOLserver itself that can be used to edit
the necessary AOLserver config. files ...
Hal Heisler and I passed this idea back and forth very briefly a
couple of months ago (almost a year or more now? I lose track of
time) ...
> There was one other technical question I had about the nsfreetds. Which
> call-level interface does it use going into freeTDS? The db-lib, ct-lib, or
> ODBC? The freetds docs say the ODBC isn't very stable yet.
The nsfreetds driver uses TDS directly. I'm not too fond of using
DB-Lib or CT-Lib ... although I probably should have used CT-Lib.
I was afraid that CT-Lib wasn't thread-safe and didn't have time
to inspect the FreeTDS folks' code. Heck, even their TDS
implementation isn't thread-safe ... I avoid as much of that
as possible.
Glad to hear you got it working!
-- Dossy
--
Dossy Shiobara mail: [EMAIL PROTECTED]
Panoptic Computer Network web: http://www.panoptic.com/
