freetds AT lists.ibiblio.org
Subject: FreeTDS Development Group
List archive
- From: Brian Bruns <camber AT ais.org>
- To: TDS Development Group <freetds AT franklin.metalab.unc.edu>
- Subject: Re: tds_login and tds_config
- Date: Tue, 15 Oct 2002 07:51:17 -0400 (EDT)
It's fine to collapse them to one structure, but you'll need one instance
per LOGINREC/CS_CONTEXT and then duplicate it for each TDSSOCKET. It'd
probably be cleaner that way, although many of the fields would be unused
in the tds_login'ish one. I like using the TDS_CHAR *, the fixed length
fields are a carry over from pre-TDS7 days where the fields where fixed
length, time to dispense with them.
Brian
On 15 Oct 2002, Frediano Ziglio wrote:
> Ok, then I think I'll do such things
>
> Rename tds_config to tds_connect_info (tds_config do not store only
> configuration information, so name seem not correct)
> Declare tds_connect_info with first fields equal to tds_config (or use a
> single field login_info)
> Write a tds_login_copy function (I'd like to rewrite tds_login with
> TDS_CHAR* fields instead of fixed buffers).
>
> freddy77
>
-
tds_login and tds_config,
Frediano Ziglio, 10/14/2002
- <Possible follow-up(s)>
- Re: tds_login and tds_config, Brian Bruns, 10/14/2002
- Re: tds_login and tds_config, Frediano Ziglio, 10/15/2002
- Re: tds_login and tds_config, Brian Bruns, 10/15/2002
Archive powered by MHonArc 2.6.24.