Re: [HACKERS] Native OLE DB. What do you think about it

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Marek Mosiewicz" <marekmosiewicz(at)poczta(dot)onet(dot)pl>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>, "PostgreSQL odbc list" <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: [HACKERS] Native OLE DB. What do you think about it
Date: 2002-06-17 08:34:21
Message-ID: GNELIHDDFBOCMGBFGEFOAEMMCCAA.chriskl@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-odbc

Are you aware that another team on the list is working on a .Net provider?
Maybe you could work with them?

.Net Provider people: speak up!

Chris

> -----Original Message-----
> From: pgsql-hackers-owner(at)postgresql(dot)org
> [mailto:pgsql-hackers-owner(at)postgresql(dot)org]On Behalf Of Marek Mosiewicz
> Sent: Monday, 17 June 2002 4:34 PM
> To: PostgreSQL-development; PostgreSQL odbc list
> Subject: [HACKERS] Native OLE DB. What do you think about it
>
>
> Hello everbody.
>
> I have started work on native OLE DB Provider for PostgreSQL. i
> think it is
> really important to have native OLE DB proviader even if there is
> OLE DB to
> ODBC Provider. Microsoft started to withdraw support for ODBC and seems to
> force to switch to OLE DB(eg VS .Net have limited support for ODBC which
> must be spearetly downloaded), so we could expect more such moves. So I
> started work on native PostgreSQL OLE DB provider. It slowly begin
> to work. (it registers to system, shows property pages, connects to
> database, and do first quries). Now I'm working on creating resultset.
>
> I would like somebody to help answer some questions:
>
> 1.is it safe to use binary cursors (basic types format e.g date would not
> change in future)
> 2.how could I control result type (binary/ASCII) for ordinary SELECTS ?
> 3.could ODBC driver mix auto-commit and FETCH/DECLARE mode ? how it can
> handle such situation:
> start select (fetch some data) /as I understand it should start
> transaction silently/
> update (it should commit as we are in auto-commit)
> fetch more data.
> next update (commit again)
> 4. maybe it would have sense to make some common library with
> ODBC to handle
> prepared statements and some kind of conversions (althougth maybe not
> becouse we convert to different types (OLE DB uses OLE Automation types))
> 5. Is there any way to truncate PQresult in libpq ? I implement
> fast forward
> cursors so i have no need to store whole result (I can read piece of data
> and forget it when client read it from me). I think there would be no
> problem if I add some PQtruncate(PQresult *) to pqlib, but maybe there is
> any different way ?
>
> I use ATL templates for OLE DB which is MS library and it can't
> be compiled
> withot Visual Studio. (you have right to distribute ATL if you bougth VS).
> So It would be not "pure" solution, but starting from scratch is to
> difficult, as I don't know COM prefectly. Maybe somebody will rewrite it
> later.
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message James Thornton 2002-06-17 09:13:48 Re: FATAL 2: InitRelink(logfile 0 seg 173) failed: No such
Previous Message Marek Mosiewicz 2002-06-17 08:33:51 Native OLE DB. What do you think about it

Browse pgsql-odbc by date

  From Date Subject
Next Message Dave Page 2002-06-17 11:48:56 Re: [HACKERS] Native OLE DB. What do you think about it
Previous Message Marek Mosiewicz 2002-06-17 08:33:51 Native OLE DB. What do you think about it