Re: [AOLSERVER] experimental alternate odbc driver available
_Please_ excuse my ignorance on this subject! In order to connect to MS SQL Server from my NetBSD box, will I still need the 'ODBC to ODBC Bridge' software with this driver? Is the free version of said package, which is limited to 'a single connection' going to work for anything more than testing? There was talk of a nstdsdb module from [EMAIL PROTECTED] Would this allow direct access to an MS SQL Server box from my NetBSD box? Thank you! By the way, I have started looking at the difficulty involved in migration from SQL Server to PostgreSQL and it is only ugly at the Stored Procedure - Function level. I stayed away from SP that return tuples, but use cursors extensively, so they would need major rewrites. On the plus side, I am going to rewrite them all in pl/Tcl! Ian A. Harding Programmer/Analyst II Tacoma-Pierce County Health Department (253) 798-3549 mailto: [EMAIL PROTECTED] [EMAIL PROTECTED] 05/02/01 03:02PM I've taken Rob Mayoff's DB2 driver, and made it ODBC 3.0 compliant. The benefits of this driver over the standard nsodbc module are: 1. Works with fields greater than 8192 chars in length 2. Max field size is settable on a per aolserver process level 3. autocommit is turned off, making transactions easier to create within your application 4. supports bind variables (Rob built various commands to handle input lists of variables and filenames -- this has been borrowed but untested.) 5. hooks for better support of lobs. DB/2 automatically could load/store lobs from files. Those hooks are in the code but have been disabled. I intend to write ODBC 3 compliant versions of the lob -- file support in the driver. You can download the driver at: http://downloads.hollyjerry.org:16080/files/aolserver3.2/odbc2.tar It's very experimental at the moment. It should have the same performance characteristics as the DB2 driver and the old nsodbc module. So enjoy, and please let me know how it works. Jerry Asher = Jerry Asher [EMAIL PROTECTED] 1678 Shattuck Avenue Suite 161Tel: (510) 549-2980 Berkeley, CA 94709Fax: (877) 311-8688
Re: [AOLSERVER] experimental alternate odbc driver available
At 09:33 AM 5/4/01 -0700, you wrote: _Please_ excuse my ignorance on this subject! In order to connect to MS SQL Server from my NetBSD box, will I still need the 'ODBC to ODBC Bridge' software with this driver? Is the free version of said package, which is limited to 'a single connection' going to work for anything more than testing? It depends on your application. Presumably it will work for a low volume app and not for a high volume app. You can presumably use, the open source unixODBC driver, I didn't in part because my client was not interested, and in part because using the supported version from easysoft got me some documentation and some useful emails that explained how things work. Please feel free to research the free unixODBC method, since the driver itself is known to work, it should now be much easier to swap out the easysoft for the unixODBC code. (And it's very much likely the same code just repackaged, since easysoft uses unixODBC themselves.) There was talk of a nstdsdb module from [EMAIL PROTECTED] Would this allow direct access to an MS SQL Server box from my NetBSD box? Presumably. Jerry = Jerry Asher [EMAIL PROTECTED] 1678 Shattuck Avenue Suite 161Tel: (510) 549-2980 Berkeley, CA 94709Fax: (877) 311-8688
Re: [AOLSERVER] experimental alternate odbc driver available
At 12:15 PM 5/4/01 -0500, you wrote: In order to connect to MS SQL Server from my NetBSD box, will I still need the 'ODBC to ODBC Bridge' software with this driver? Apparently, yes. Jerry? You've been working with that config. Yes, you will need something, I have not looked to see if unixODBC or easysoft or whatever runs on NetBSD. Jerry = Jerry Asher [EMAIL PROTECTED] 1678 Shattuck Avenue Suite 161Tel: (510) 549-2980 Berkeley, CA 94709Fax: (877) 311-8688
[AOLSERVER] Has server.log rolling ever worked?
Umm, I guess I should know the answer to this, but I don't: Has anyone gotten their server.log to roll automatically? Kris
Re: [AOLSERVER] Has server.log rolling ever worked?
On Fri, 4 May 2001, Kris Rehberg wrote: Umm, I guess I should know the answer to this, but I don't: Has anyone gotten their server.log to roll automatically? You mean aside from kill -HUP `cat ns.pid`? That's what we do. Note that you have to turn off the HUP log rolling of the access log, else you may delete your access logs if you time it right. (the RollOnsignal variable) Kris -- Michael Matthews, CCB, [EMAIL PROTECTED] | [EMAIL PROTECTED] | x50984
Re: [AOLSERVER] Has server.log rolling ever worked?
As far as I know, it does, unless someone else is doing it for me. dave On Fri, 4 May 2001, Kris Rehberg wrote: Umm, I guess I should know the answer to this, but I don't: Has anyone gotten their server.log to roll automatically? Kris -- Dave Weis I believe there are more instances of the abridgement [EMAIL PROTECTED] of the freedom of the people by gradual and silent encroachments of those in power than by violent and sudden usurpations.- James Madison
Re: [AOLSERVER] Has server.log rolling ever worked?
Kris Rehberg [EMAIL PROTECTED] writes: Has anyone gotten their server.log to roll automatically? I use the following: ns_section ns/parameters ns_param serverlog smc.log ns_param logroll true ns_param maxbackup 14 ...but it doesn't work. :-( The name is used, but there's no rolling. -tih -- The basic difference is this: hackers build things, crackers break them.
Re: [AOLSERVER] experimental alternate odbc driver available
I am trying to install unixODBC right now, but keep getting a pernicious error from the linker. It does not like the way it is getting passed flags. I had this same problem with compiling PostgreSQL. I am having more trouble tracking it down this time. I think it must be NetBSD specific. Ian A. Harding Programmer/Analyst II Tacoma-Pierce County Health Department (253) 798-3549 mailto: [EMAIL PROTECTED] [EMAIL PROTECTED] 05/04/01 10:02AM At 09:33 AM 5/4/01 -0700, you wrote: _Please_ excuse my ignorance on this subject! In order to connect to MS SQL Server from my NetBSD box, will I still need the 'ODBC to ODBC Bridge' software with this driver? Is the free version of said package, which is limited to 'a single connection' going to work for anything more than testing? It depends on your application. Presumably it will work for a low volume app and not for a high volume app. You can presumably use, the open source unixODBC driver, I didn't in part because my client was not interested, and in part because using the supported version from easysoft got me some documentation and some useful emails that explained how things work. Please feel free to research the free unixODBC method, since the driver itself is known to work, it should now be much easier to swap out the easysoft for the unixODBC code. (And it's very much likely the same code just repackaged, since easysoft uses unixODBC themselves.) There was talk of a nstdsdb module from [EMAIL PROTECTED] Would this allow direct access to an MS SQL Server box from my NetBSD box? Presumably. Jerry = Jerry Asher [EMAIL PROTECTED] 1678 Shattuck Avenue Suite 161Tel: (510) 549-2980 Berkeley, CA 94709Fax: (877) 311-8688
[AOLSERVER] [ aolserver-Bugs-421459 ] ns_passwordcheck inverts logic
Bugs item #421459, was updated on 2001-05-04 11:58
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=103152aid=421459group_id=3152
Category: API: Tcl
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Jerry Asher (jerryasher)
Assigned to: Nobody/Anonymous (nobody)
Summary: ns_passwordcheck inverts logic
Initial Comment:
From the documentation:
ns_passwordcheck ?-server servername? user password
Description
This function returns 1 (one) if the user and password
combination is legitimate. It returns 0 (zero) if
either the user does not exist or the password is
incorrect. If no servername is specified, the current
virtual server is used.
From the code (nsperm/compat.tcl)
# compat.tcl -
proc ns_passwordcheck { user password } {
set ret [catch {ns_perm checkpass $user $password}
err]
if {$ret == 0} {
return 0
} else {
return 1
}
}
Now catch returns 0 when all is fine, and 1 when there
is an error, and ns_perm checkpass tosses an error
when the password is NOT correct or there the user
does not exist.
Hence, ret will be 0 when all is fine and
ns_passwordcheck will return a 0 when all is fine.
Either the doc or the code needs to be fixed -- I
suggest the code.
--
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=103152aid=421459group_id=3152
Re: [AOLSERVER] Has server.log rolling ever worked?
Tom Ivar Helbekkmo [EMAIL PROTECTED] writes:
Kris Rehberg [EMAIL PROTECTED] writes:
Has anyone gotten their server.log to roll automatically?
I use the following:
ns_section ns/parameters
ns_param serverlog smc.log
ns_param logroll true
ns_param maxbackup 14
...but it doesn't work. :-( The name is used, but there's no
rolling.
nslog is working for me with the following config:
ns_section ns/server/${service_short_name}/module/nslog
ns_param EnableHostnameLookup Off
ns_param File ${AOL_HOME}/log/${service_short_name}.log
ns_param LogCombined On
ns_param LogRefer Off
ns_param LogUserAgent Off
ns_param MaxBackup 5
ns_param RollDay *
ns_param RollFmt %Y-%m-%d-%H:%M
ns_param RollHour 0
ns_param RollOnSignal On
ns_param RollLog On
Dave
Re: [AOLSERVER] Has server.log rolling ever worked?
Yikes! My server.log is 250 MB! However, access.log is rolling nicely. Ian A. Harding Programmer/Analyst II Tacoma-Pierce County Health Department (253) 798-3549 mailto: [EMAIL PROTECTED] [EMAIL PROTECTED] 05/04/01 11:27AM Umm, I guess I should know the answer to this, but I don't: Has anyone gotten their server.log to roll automatically? Kris
Re: [AOLSERVER] TDS database driver for AOLserver
On 2001.05.04, Ian Harding [EMAIL PROTECTED] wrote: There was talk of a nstdsdb module from [EMAIL PROTECTED] Would this allow direct access to an MS SQL Server box from my NetBSD box? Upon closer inspection of the Sybase Open Client FAQ, it seems that SQL Server 7 and newer use a new client-server protocol and that TDS is now a legacy protocol: http://www.isug.com/Sybase_FAQ/ASE/section7.html#7.4 However, it seems that it is still possible to connect to SQL Server 7 using TDS if you apply Service Pack 2 of SQL Server 7, according to the FAQ. I'm grabbing a copy of FreeTDS this weekend and seeing if I can get at least a bare-bones driver working, perhaps shamelessly stealing from the nssybpd external DB driver. Perhaps, I'll even be so lazy as to just try and get nssybpd working using FreeTDS instead of the Sybase Open Client libraries. Of course, as I've said before, I don't have a SQL Server set up here, but others have offered to volunteer theirs -- if they're accessible over the Internet (not firewalled, etc.) and an account can be set up, please email me. I'd like to test against a SQL Server 6, 7, and 2000 ... if possible. I'll be able to test against SQL Server 2000 and I believe SQL Server 7 at work next week, but I don't know if SQL Server 6 is installed anywhere any more. - Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/
Re: [AOLSERVER] TDS database driver for AOLserver
But if you look at the FreeTDS site, their 4.2 version talks to SQL Server 7, and their 7.0 version talks to uppity SQL Server 7 and SQL Server 2000. I've been working on this off and on all week. I'll race ya. Dossy wrote: On 2001.05.04, Ian Harding [EMAIL PROTECTED] wrote: There was talk of a nstdsdb module from [EMAIL PROTECTED] Would this allow direct access to an MS SQL Server box from my NetBSD box? Upon closer inspection of the Sybase Open Client FAQ, it seems that SQL Server 7 and newer use a new client-server protocol and that TDS is now a legacy protocol: http://www.isug.com/Sybase_FAQ/ASE/section7.html#7.4 However, it seems that it is still possible to connect to SQL Server 7 using TDS if you apply Service Pack 2 of SQL Server 7, according to the FAQ. I'm grabbing a copy of FreeTDS this weekend and seeing if I can get at least a bare-bones driver working, perhaps shamelessly stealing from the nssybpd external DB driver. Perhaps, I'll even be so lazy as to just try and get nssybpd working using FreeTDS instead of the Sybase Open Client libraries. Of course, as I've said before, I don't have a SQL Server set up here, but others have offered to volunteer theirs -- if they're accessible over the Internet (not firewalled, etc.) and an account can be set up, please email me. I'd like to test against a SQL Server 6, 7, and 2000 ... if possible. I'll be able to test against SQL Server 2000 and I believe SQL Server 7 at work next week, but I don't know if SQL Server 6 is installed anywhere any more. - Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/
Re: [AOLSERVER] TDS database driver for AOLserver
On 2001.05.04, Michael Roberts [EMAIL PROTECTED] wrote: But if you look at the FreeTDS site, their 4.2 version talks to SQL Server 7, and their 7.0 version talks to uppity SQL Server 7 and SQL Server 2000. Oh, the Sybase FAQ does say that connecting _is_ possible, but it requires an application of a SQL Server Service Pack 2 from Microsoft. I'm not sure if the service pack is _necessary_ in order for connections to work, but that's the impression I got, at least. I've been working on this off and on all week. I'll race ya. You're on. It's ... 10:19 PM now. Assuming FreeTDS takes less than 20 minutes to compile on my dev. box, I'll hopefully be connecting to Sybase by 11:00 PM. If someone can set me up an account on a SQL Server box before 11:00 PM, I'll hopefully be connecting to it by midnight tonight. ;-P So, who's volunteering to set me up a username/password on their publically accessible SQL Server box? - Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/
Re: [AOLSERVER] TDS database driver for AOLserver
Good news, all, It's now 1:10 AM, and I've got the beginnings of the nsfreetds driver. (Yes, that's what I've decided to call it.) Some details about the driver's current state: * I haven't tested this with anything but SELECT statements, DML may fail. * The driver only supports columns of max size 255 characters. It has a buffer overrun because of this current limit. * The driver is most likely not thread-safe. I've already identified the areas in the driver that are questionable, and will be addressing it soon. If you get strange result sets back, perhaps someone else is running a query at the same time. Surprise! Anyhow, this is a good proof-of-concept, and I want to thank all of you for contributing a SQL Server for me to test against. Hopefully in a short amount of time the driver will be complete enough to release as a v0.1 release, and we can get some serious testing going on. Then, I can think about compiling a Win32 build of it, and checking it into AOLserver CVS. - Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/
