-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ce message peut être intéressant aux gens qui utilisent unixODBC et PostgreSQL. NOTE: La trace de unixODBC génére BEAUCOUP de résultats! Environ 59k pour une simple requête comme "select * from users where last_name='Rossen'" fait avec isql. Erik Rossen ^ [EMAIL PROTECTED] /e\ http://www.multimania.com/rossen --- GPG key ID: 2935D0B9 - ---------- Forwarded message ---------- Date: Fri, 22 Sep 2000 12:31:32 +0000 From: Nick Gorham <[EMAIL PROTECTED]> To: Erik Rossen <[EMAIL PROTECTED]> Subject: Re: bug reports, fixes, and feature requests for unixODBC Erik Rossen wrote: > > I've managed to unixODBC-1.8.12 installed and working with StarOffice 5.1 > on a Debian 2.2 i86 system without too much difficulty, but I had a few > problems that could be (should be) easily fixed: > > 1. The default ./configure comes with --enable-static. You might want to > switch that to --disable-static since it is usually redundant (IMHO). Can > you tell that I don't have much room left on my hard disk? ;-) Good idea. > 2. There are files missing from the gODBCConfig subdirectory that are > necessary for ./configure to work there. I was able to copy them from the > parent directory and ./configure worked afterwards. They are: > > config.sub > config.guess > ltconfig > ltmain.sh These should be generated by running autogen.sh, should be documented > 3. It would be nice if you could clarify where one comments-out unwanted > Drivers in the Drivers Makefile (which doesn't exist before ./configure, > naturally). For example, is it sufficient to just edit Makefile.am? I > don't have enough experience with autoconf and the autoconf info pages say > nothing about Makefile.am. Remove them from Makefile.am and configure.in then run autoconf the ./configure again. 4. A man page for isql (and everything else :-) would be nice. Good point, I will try and sort one out. > > 5. Under Debian the PostgreSQL socket is > /var/run/postgresql/.s.PGSQL.5432, NOT /tmp/.s.PGSQL.5432 ! It would be > nice if unixODBC detected automatically where the sockets were or allowed > one to specify them in gODBCConfig, but in the meantime you can just tell > everyone to go netstat -l to see exactly where the database sockets are > and then make appropriate symbolic links to them, for example: > ln -s /var/run/postgresql/.s.PGSQL.5432 /tmp/.s.PGSQL.5432 I will remember that, thanks. The original postgres driver only connects via tcp not unix domain sockets, so this wont have come up before. > 6. Is there some trick to getting the unixODBC trace file to work? It > doesn't work for me with this /usr/local/etc/odbc.ini file: Yes, it got changed. In the odbcinst.ini file add the following [ODBC] Trace = yes Trace File = /tmp/sql.log I moved it, otherwise you can't trace before a connection is made, which makes debugging connection problems a tad diffucult :-) > 7. By the way, I am using PostgreSQL 6.5 rather than 6.4. Are there any > known problems with that? Not that I am aware, it also works with 7 FWIW - -- Nick Gorham Easysoft Ltd -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.0 (GNU/Linux) Comment: Made with pgp4pine 1.75 iD8DBQE5y2S3Y88aPik10LkRAr9ZAJ90uNVguM6RSMZz7V/sPDXjsx97DQCdHmgQ AKrZoW6UsYMPh6ezZekA9dA= =pq17 -----END PGP SIGNATURE----- -- http://www-internal.alphanet.ch/linux-leman/ avant de poser une question.
