From: Adam Lang <aalang@rutgersinsurance.com>
To: pgsql-interfaces@postgresql.org
To: Jamie Walker <jamie@sagaxis.co.uk>
Subject: Re: Re: new maintainer for the ODBC driver?
Date: Fri, 27 Oct 2000 09:01:24 -0400
Message-ID: <008c01c04016$02d5d440$330a0a0a@6014cwpza006> (raw)
References: <39F6F180.C187BD39@alumni.caltech.edu>
<Pine.LNX.4.10.10010261603500.3001-100000@tir>
<BdyVOSAxuM+5EwsJ@sagaxis.co.uk>
Oh geez! I'm almost forgot, I do have a copy of Turbo C++ 4.5 (I think).
Wow... That C class I took really must have fallen into the back of my mind.
Again, I have no clue if they are appropriate for compiling the ODBC
driver.
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
----- Original Message -----
From: "Jamie Walker" <jamie@sagaxis.co.uk>
To: <pgsql-interfaces@postgresql.org>
Sent: Thursday, October 26, 2000 8:26 PM
Subject: Re: [INTERFACES] Re: new maintainer for the ODBC driver?
> In article <Pine.LNX.4.10.10010261603500.3001-100000@tir>, kovacsz
> <zoli@pc10.radnoti-szeged.sulinet.hu> writes
>
> >There must be (at least---and in my opinion at most) one man ("the
> >patcher") who is responsible for patching the source with the new codes.
> >As Byron wrote, each change should be tested by at least 4 people. So I
> >don't think it would be useful to change the CVS immediately, only after
> >every tester reported that the new version works well.
> I thought the whole point of a CVS tree was that it was current i.e. not
> guaranteed to be bug free. The sources can be marked with release tags
> when they are considered stable. This would mean that you can have a
> virtually unlimited number of people testing the code.
> >
> >Respecting to Cedar's opinion about the free C compilers, I know that the
> >Borland C++ 5.5 command-line compiler is free, but I never used it. Other
> >possibilites are DJGPP which perhaps could create DLLs (but I also never
> >used it for making any code for Windows). CygWin can be also a solution.
> >This week I would like to try all these (th/f)ree compilers with the ODBC
> >source.
> There is another compiler called 'mingw32', which is a native GCC
> distribution for Windows - I don't know if it is properly maintained.
> The other option would be to use a cross compiler.
>
> >IMHO, the ODBC driver at the current state is a great one, so it's worth
> >to continue the work on it. Have you got any statistics about the number
> >of people using the driver at the moment?
> Me me me! I use it for a hospital database system. And it works very
> well!
> --
> Jamie Walker "While there are no known bugs in it, it might
> jamie@sagaxis.co.uk destroy your filesystems, eat your data and
> http://www.sagaxis.co.uk/ start World War III. You have been warned."
>
>
>
> ________________________________________________________
> 1stUp.com - Free the Web
> Get your free Internet access at http://www.1stUp.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: aalang@rutgersinsurance.com, jamie@sagaxis.co.uk
Subject: Re: Re: new maintainer for the ODBC driver?
In-Reply-To: <008c01c04016$02d5d440$330a0a0a@6014cwpza006>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox