Re: ODBC driver for Windows & future... - Mailing list pgsql-odbc
From | Matthew Schwartz |
---|---|
Subject | Re: ODBC driver for Windows & future... |
Date | |
Msg-id | 41AC4313.9070701@citizensurveys.com Whole thread Raw |
In response to | ODBC driver for Windows & future... ("Philippe Lang" <philippe.lang@attiksystem.ch>) |
List | pgsql-odbc |
Philippe Lang wrote:
I am not at the level where I feel that I could even assist with writing an odbc driver, but would like to do what I can to help. I follow the odbc threads with interest as I have committed to postgres.
I use postgres on a daily basis and have proven it to be a robust, reliable system- it is a phenomenal product with great potential. As a user of versions 7.2 and 7.4, I know that there are certain problems that need fixing before the odbc driver is complete and enterprise ready.
Please, someone, help sort out this problem and make sure that odbc will be viable in the future.
HelloHi, I think I'm not the only one to get worried about the future of the PGSQL ODBC driver. Since Iroshi has left last year, I have seen fixes now and then, but nobody seems to understand anymore how the driver really works... What most surprises me, is that there is not viable commercial alternative to the open-source ODBC driver. All the commercial drivers I have tested do not work at all... On the opposite, the PGSQL .NET driver development seems to be quite active, so does that mean ODBC is dead? I'm sure we are really a lot out here to be interested in a clean ODBC driver for Windows. If it continues like this, Postgresql will end up being a fantastic database, but cut out from the rest of the world. Well, the ODBC world at least. So, what next? 1. Does the driver have to be completely rewritten? I have heard of a new 7.4 protocol that the actual driver does not support, and of libpq, that could be used to access the database, but really, that's all I know... Can these changes be incorporated in the actual driver? 2. Can anyone draw a skeleton of the how the "ideal" driver should be architectured? I remember seeing quite a lot of volunteers a few months ago, and I'm willing to do so myself, but "developing an ODBC driver" is not something we do every morning before coffee... Anyway, thanks to all of you that bring something to open-source. Postgresql through ODBC is still a viable production technology, I notice it every day. I'm just worring about the future... ---------------------------------- Philippe Lang Attik System rte de la Fonderie 2 1700 Fribourg Switzerland http://www.attiksystem.ch Tel: +41 (26) 422 13 75 Fax: +41 (26) 422 13 76 GSM: +41 (79) 351 49 94 Email: philippe.lang@attiksystem.ch Skype: philippe.lang ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
I am not at the level where I feel that I could even assist with writing an odbc driver, but would like to do what I can to help. I follow the odbc threads with interest as I have committed to postgres.
I use postgres on a daily basis and have proven it to be a robust, reliable system- it is a phenomenal product with great potential. As a user of versions 7.2 and 7.4, I know that there are certain problems that need fixing before the odbc driver is complete and enterprise ready.
Please, someone, help sort out this problem and make sure that odbc will be viable in the future.
--
___________________________________________________________ |
Matthew Schwartz Citizen Surveys South Africa tel: 021 447 4484 fax: 021 448 6312 cell: 083 774 2420 email: matthew@citizensurveys.com |
---------------------------------------------------------------- This email is intended only for the use of the individual or entity named above and may contain information that is confidential and privileged. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this email is strictly prohibited. Opinions, conclusions and other information in this message that do not relate to the official business of our firm shall be understood as neither given nor endorsed by it. ---------------------------------------------------------------- |
Attachment
pgsql-odbc by date: