Re: [INTERFACES] Naming of the PostreSQL ODBC .dll file
От | Byron Nikolaidis |
---|---|
Тема | Re: [INTERFACES] Naming of the PostreSQL ODBC .dll file |
Дата | |
Msg-id | 3537CFBA.6A4C7121@insightdist.com обсуждение исходный текст |
Ответ на | Naming of the PostreSQL ODBC .dll file ("Julia A.Case" <julie@hub.org>) |
Ответы |
Re: [INTERFACES] Naming of the PostreSQL ODBC .dll file
Re: [INTERFACES] Naming of the PostreSQL ODBC .dll file |
Список | pgsql-interfaces |
Julie, Well, the driver is now 32 bit and 16 bit support would be very difficult to add and would degrade the driver's performance and supportability, as I already stated. I think it would be moving backwards for this development effort. We haven't heard any complaints yet about the lack of 16 bit support. Why dont we just keep going in a forward direction and see what happens. It seems to work for Bill Gates. He's no friend of mine, but he sure knows how to get software to market. Byron Julia A.Case wrote: > Quoting Byron Nikolaidis (byronn@insightdist.com): > > That was one of the biggest changes with this driver. It no longer supports > > 16 bit windows. All the messy Dummy Handle Lists that used to be mainted were > > eliminated and now the handle is the pointer to the structure for all the > > Statement functions. The old driver used GlobalAlloc and GlobalLock to handle > > 16 bit because the pointer returned by malloc may be moved and is not > > sufficient to be used for a handle. In 32 bit windows, you can safely use > > malloc. > > > The last time I made mumblings of droping 16 bit support I got > roasted pretty good. There seem to still be a lot of 16 bit users out > there that would like to use the driver. > > Julie
В списке pgsql-interfaces по дате отправления: