On Tue, 2004-03-09 at 21:13, Dossy wrote:
> Before you go down that path, can we just figure out what needs to
> change in nsodbc to use unixODBC as an ODBC Manager? It seems kind of
> ridiculous that we have more than one nsodbc-like driver for AOLserver
> and it'd be nice to have just one that
On 2004.03.09, Tom Jackson <[EMAIL PROTECTED]> wrote:
>
> Yes! there is a definite problem, although being dumb at C, I was unable
> to pin down the exact problem and how to fix it, but the defined types
> seems to have changed, or was different, between what was in the solid
> driver and what is i
On Tue, 2004-03-09 at 18:34, Dossy wrote:
> It's not overly aggressive and it's likely not buggy. It's telling you
> that you have prototypes which don't match the function definitions, and
> worse, the prototypes coerce a different promotion of types than the
> function definition would. These
On 2004.03.08, Bob Woodside <[EMAIL PROTECTED]> wrote:
>
> [Grumble.] The culprit is the -Wconversion flag set in
> $(NSHOME)/include/Makefile.global. Without it, all the warnings go away.
> Short of killing this flag, I couldn't coerce gcc to be happy with any
> amount of typecasting.
Hah
On Sun, 7 Mar 2004 21:09:24 -0800
Tom Jackson <[EMAIL PROTECTED]> wrote:
> Ah, yes the compiler warnings. Essentially the defines which set the
> data type are messed up. Small Int/Unsigned Int, something like that
> it seems. I think these are warnings which used to not show up in
> older version
On Sun, 7 Mar 2004 21:09:24 -0800
Tom Jackson <[EMAIL PROTECTED]> wrote:
> On Sun, 2004-03-07 at 20:45, Bob Woodside wrote:
>
> > Actually, the first thing I thought I'd look into is
> > puzzling out some of those compiler warnings.
>
> Ah, yes the compiler warnings. Essentially the defin
On Sun, 2004-03-07 at 20:45, Bob Woodside wrote:
> > The first change should probably be a separate bindvar module, as
> > Andrew suggested, then add bind var usage in nsunixodbc.
>
> Keep us posted if you guys do anything along those lines. Actually, the
> first thing I thought I'd look i
On Sun, 7 Mar 2004 10:32:40 -0800
Tom Jackson <[EMAIL PROTECTED]> wrote:
> On Sun, 2004-03-07 at 06:33, Bob Woodside wrote:
> > I see that nsunuxodbc has gotten added to the list - has it
> > got any
> > changes from the one I downloaded last Tuesday?
>
> What list? I haven't made
On Sun, 2004-03-07 at 06:33, Bob Woodside wrote:
> I see that nsunuxodbc has gotten added to the list - has it got any
> changes from the one I downloaded last Tuesday?
What list? I haven't made any changes. Thanks for the report on your
progress. If you would send me a generic configurati
On Tue, 2 Mar 2004 11:22:17 -0800
Tom Jackson <[EMAIL PROTECTED]> wrote:
> I asked Scott G about including this in the SF modules section, but it
> is on hold pending a review of the code.
> Also at issue is whether there should be one odbc driver.
> My opinion is there should be one driver per od
On Tue, 2004-03-02 at 20:43, Andrew Piskorski wrote:
> Um, just what "stored procedures" are you talking about here? Where
> are these examples or docs that you're looking at? This has nothing
> to do with ODBC per-se, right? The only "stored procedures" I know
> about are stuff like Oracle PL/
On Tue, Mar 02, 2004 at 05:31:57PM -0800, Tom Jackson wrote:
> On Tue, 2004-03-02 at 16:55, Andrew Piskorski wrote:
> Umm, I think I was definitely confused by the idea of stored procedures.
> Initially I thought they were just named procedure calls already in the
> database. Somewhere along the w
> On Tue, 2004-03-02 at 16:55, Andrew Piskorski wrote:
>> Hm, maybe that should actually be movded into the standard ns_db API?
No - it's the wrong thing to do with any database that implements
variables that can be assigned values and later used in SQL queries.
Is Oracle the only popular RDBMS
On Tue, 2004-03-02 at 16:55, Andrew Piskorski wrote:
> I did not work right when I tried it (strange errors; ...
For me, nsodbc didn't even compile.
> :) Well, I still have it in my local CVS. Looks like I just copied
> 480 lines of bind variable emulation code from postgres.c rev. 1.31
> 2001/
On Tue, Mar 02, 2004 at 12:14:35PM -0800, Tom Jackson wrote:
> On Tue, 2004-03-02 at 11:29, Andrew Piskorski wrote:
>
> > Hm, I'd forgotten about that. Tom, how did work on your ODBC/nssolid
> > driver for use with unixodbc go? And can you tell us something about
> > why using the nssolid driver
On Tue, 2004-03-02 at 14:37, Dossy wrote:
> I definitely think there should be ONE ODBC module (the term "ODBC
> driver" actually refers to what the ODBC manager uses to connect to the
> DB itself), and if a particular driver manager needs special code in the
> nsodbc module to work, then we condit
On 2004.03.02, Tom Jackson <[EMAIL PROTECTED]> wrote:
> Also at issue is whether there should be one odbc driver. My opinion
> is there should be one driver per odbc driver manager (unixodbc being
> a driver manager), because each driver manager supports different
> features and different database
On Tue, 2004-03-02 at 11:55, Andrew Piskorski wrote:
> Huh? Are you saying that bind variables and stored procedures are in
> some way comparable to or a replacement for each other? How does that
> work?
No they are not comparable. Maybe it could work for
insert/update/delete, but looks not fun.
On Tue, 2 Mar 2004 11:22:17 -0800
Tom Jackson <[EMAIL PROTECTED]> wrote:
> Bob,
> I just put up a copy of the current code.
> You can get it at http://zmbh.com/nsunixodbc/
Super! I'll grab it and try it out, probably this evening.
[/me watches bits fly across the NIC]
On Tue, 2004-03-02 at 11:29, Andrew Piskorski wrote:
> Hm, I'd forgotten about that. Tom, how did work on your ODBC/nssolid
> driver for use with unixodbc go? And can you tell us something about
> why using the nssolid driver code was a better starting point than
> either nsodbc or Jerry Asher's
On Tue, Mar 02, 2004 at 11:22:17AM -0800, Tom Jackson wrote:
> I'm hoping to get around to adding stored procedures, but haven't done
> so yet. The driver also doesn't support bind vars yet. Not sure which to
> add, but it seems the way to go with odbc is to use stored procedures,
> not bind vars.
On Tue, Mar 02, 2004 at 12:58:29PM -0500, Bob Woodside wrote:
> On Sun, 4 Jan 2004 10:35:09 -0800, Tom Jackson wrote:
>
> > I was trying to use unixodbc (www.unixodbc.org) and was hoping
> > to find a template to use for the driver. nsodbc wasn't it, but
> > nssolid was!
>
> This sounds lik
Bob,
I just put up a copy of the current code.
I have adapted the nssolid driver, fixing a few bugs and changing the
naming of the commands, etc.
I asked Scott G about including this in the SF modules section, but it
is on hold pending a review of the code.
Also at issue is whether there should be
(Sorry this isn't properly threaded -- I just joined the list.)
On Sun, 4 Jan 2004 10:35:09 -0800, Tom Jackson wrote:
> I was trying to use unixodbc (www.unixodbc.org) and was hoping
> to find a template to use for the driver. nsodbc wasn't it, but
> nssolid was!
This sounds like
On Sun, 2004-01-04 at 02:22, Andrew Piskorski wrote:
> On unix, there are two or so different open source ODBC projects that
> you should be able to use for this, but I've never tried them. MS
> Windows (which version, NT?) includes an ODBC driver manager so on
> Windows, here are some really anc
On Sat, Jan 03, 2004 at 06:00:23PM -0800, Tom Jackson wrote:
> How do you compile the odbc driver? There is the RedBrick option and
> generic. Generic needs sql.h, and other headers. I guess I need some
> other package somewhere?
You definitely need a 3rd party ODBC "driver manager" in order to us
How do you compile the odbc driver? There is the RedBrick option and
generic. Generic needs sql.h, and other headers. I guess I need some
other package somewhere?
TIA
tom jackson
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECT
27 matches
Mail list logo
