Skip site navigation (1) Skip section navigation (2)

Re: New ODBC driver

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: <markw(at)mohawksoft(dot)com>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: New ODBC driver
Date: 2004-12-01 16:27:57
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4527C11@ratbert.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgsql-odbc
 

> -----Original Message-----
> From: markw(at)mohawksoft(dot)com [mailto:markw(at)mohawksoft(dot)com] 
> Sent: 01 December 2004 16:21
> To: Dave Page
> Cc: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] New ODBC driver
> 
> >
> >
> >> -----Original Message-----
> >> From: markw(at)mohawksoft(dot)com [mailto:markw(at)mohawksoft(dot)com]
> >> Sent: 01 December 2004 15:02
> >> To: Dave Page
> >> Cc: pgsql-odbc(at)postgresql(dot)org
> >> Subject: Re: [ODBC] New ODBC driver
> >>
> >> > I don't think it would be realistic to mix the two
> >> approaches though -
> >> > if only because they couldn't share a single database connection.
> >>
> >> Why is this an issue? Why not create multiple connections?
> >
> > Efficiency for a start - but what would you use each for? Any 
> > application developer is going to expect everything to use the same 
> > connection - how do you direct a 'SET' statement? What about 
> > transaction isolation?
> >
> > Regards, Dave.
> 
> OK, I'm going to take a look at it.
> 
> I have a stupid question, where is the location of the ODBC 
> source? Is it part of PostgreSQL?
> 

http://gborg.postgresql.org/project/psqlodbc, in the CVS section.

Regards, Dave,

pgsql-odbc by date

Next:From: SimeĆ³ ReigDate: 2004-12-01 16:28:08
Subject: Re: ODBC driver for Windows & future...
Previous:From: markwDate: 2004-12-01 16:20:54
Subject: Re: New ODBC driver

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group