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

Next development steps?

From: Ludek Finstrle <luf(at)pzkagis(dot)cz>
To: pgsql-odbc(at)postgresql(dot)org
Subject: Next development steps?
Date: 2005-12-14 14:39:20
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-odbc

  I study the driver and there are lot of code which doesn't work since
libpq support. (e.g.) There is support for updatable cursor which doesn't
work (if I'm right) because it's using backend_tuples which isn't

  It seems no other (except swamped Dave and Anoop) is supporting ODBC
driver. I propose these steps:

1) clean the code (and UI) with drop all non-trivial features
   - these features make the code unreadable and complicated with
     no proper behaviour right now
   - there is no error report for them since libpq support
     (exclude [#1000413] Optimistic lock cannot be used with updateable
      cursors - I think updateable cursor doesn't work at all)
2) create better transaction support (see Marco Ristola post)
3) improve libpq support to use PQprepare, bind parameters
4) full support for only_forward read-only cursor
5) create small steps in support dropped things
and so on ...

Can we create a new development branch at least?

What do you think about it?



pgsql-odbc by date

Next:From: Hiroshi SaitoDate: 2005-12-14 15:30:38
Subject: Re: Next development steps?
Previous:From: Dave PageDate: 2005-12-14 14:19:03
Subject: Re: ODBC driver failure

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