Try Command Prompt's ODBC driver. Lately it has been measured to be
consistently faster than psqlODBC.
http://projects.commandprompt.com/public/odbcng
Thanks,
I tried this, but via Access it always reports a login (username/password)
to db failure. However, this a an Alpha - is there an
carlo: please, please, get your mail server to quit telling me your
mailbox is full :)
Merlin, sorry about that. This is the first I've heard of it.
Carlo
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Yeah, but they had to back-off from that plan, and AFAIK it only uses
libpq for the auth stuff and then switch to dealing with the protocol
directly.
I don't know what the reasoning was though :-) I guess Joshua would
know. I'm not involved in that project. I only know that recently a
On 10/21/06, Carlo Stonebanks [EMAIL PROTECTED] wrote:
Our Windows-based db server has to integrate with users that work regularily
with Access.When attempting to import user's data from Access MDB files to
PostgreSQL, we try on eof two things: either import using EMS SQL Manager's
Data Import
Carlo Stonebanks wrote:
Our Windows-based db server has to integrate with users that work regularily
with Access.When attempting to import user's data from Access MDB files to
PostgreSQL, we try on eof two things: either import using EMS SQL Manager's
Data Import from Access utility, or
On 10/21/06, Alvaro Herrera [EMAIL PROTECTED] wrote:
Carlo Stonebanks wrote:
Our Windows-based db server has to integrate with users that work regularily
with Access.When attempting to import user's data from Access MDB files to
PostgreSQL, we try on eof two things: either import using EMS
Try Command Prompt's ODBC driver. Lately it has been measured to be
consistently faster than psqlODBC.
http://projects.commandprompt.com/public/odbcng
just curious: what was the reasoning to reimplement the protocol stack
in odbcng? the mainline odbc driver went in the other direction.
ODBC is often blamed for this sort of thing - I have the 8.01.02
release
dated 2006.01.31. Everything appears to be at its default setting.
Try Command Prompt's ODBC driver. Lately it has been measured to be
consistently faster than psqlODBC.
I should note that we need to get a build
