From: | "William ZHANG" <uniware_at_zedware_dot_org(at)antispam(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: OLE DB driver |
Date: | 2004-01-10 02:32:46 |
Message-ID: | btno9k$2g8j$1@news.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Shachar Shemesh" <psql(at)shemesh(dot)biz> wrote:3FFF1607(dot)9090806(at)shemesh(dot)biz(dot)(dot)(dot)
> Andreas Pflug wrote:
>
> > I wonder if this could be implemented as a wrapper around libpq. This
> > way, the OLEDB driver would benefit from a proven piece of software.
> >
> > Regards,
> > Andreas
>
> That's what I'm doing. I'm not sure why other drivers didn't do that as
> well (maybe there was no native Windows port of libpq at the time?).
AFAIK, rely on libpq is a fast way but not always convenient.
OLEDB has many features borrowed from ODBC, and it is a
substitute for ODBC. Microsoft is now making ODBC obsolete and
advocating OLEDB instead. You'd better read pgodbc's source
code, too.
>
> My reason is actually that I'm not a great postgres hacker, and I would
> rather rely as little as possible on internal structures and things that
> are likely to change in the future.
>
> Shachar
>
> --
> Shachar Shemesh
> Lingnu Open Systems Consulting
> http://www.lingnu.com/
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Brown | 2004-01-10 12:36:06 | Re: psql \d option list overloaded |
Previous Message | Andrew Dunstan | 2004-01-09 22:50:37 | Re: Encoding problems in PostgreSQL with XML data |