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

Re: Re: unixODBC again :-(

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Nick Gorham <nick(at)lurcher(dot)org>
Cc: peter_e(at)gmx(dot)net, pgsql-hackers(at)postgreSQL(dot)org, pgsql-odbc(at)postgreSQL(dot)org
Subject: Re: Re: unixODBC again :-(
Date: 2001-01-24 23:47:33
Message-ID: 200101242347.SAA17695@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-odbc
Glad these items are being resolved.  THis has sat around too long. 
Please keep discussing and come up with a good patch.  We will help
however we can.


> peter_e(at)gmx(dot)net wrote:
> 
> > Nick Gorham writes:
> >
> > > Well because the driver does not know where to get the config info
> > > from,
> >
> > Then the driver should be fixed to do that, with or without unixODBC.
> 
> Well yes, but again, using the Windows situation as a model (not that
> I would normally suggest windows as a role model for anything), its not the
> drivers job to know or care where the info comes from, that the job of the
> (a) driver manager.
> 
> > > libodbcinst.so in unixODBC provides SQLGetPrivateProfileString,
> > > the location of user and system ini files are defined by this lib, if
> > > it doesn't do this you may have the situation where the driver manager
> > > gets information from one ini file and the driver from a different
> > > one.
> >
> > --with-odbcinst=DIRECTORY
> 
> Yes but there are two places, the user ~/.odbc.ini directory, and the
> system /sysconfdir/odbc.ini.
> 
> using the odbcinst lib, means all drivers can use the same info store, and
> you can just install a binary driver without having to set any
> configuration.
> 
> > > > > Add the option to detect a
> > > > > server name of localhost, and open the unix domain socket,
> > > >
> > > > I don't think so.  localhost is a valid host name.
> > >
> > > Ok, but don't you think it is worth having some way to get it to use
> > > UNIX domain sockets instead of TCP ones, for instance if postmaster
> > > isn't started with a -i ?
> >
> > Yes, that would be okay, but it's not okay to eliminate a feature to add
> > another one.
> 
> I would agree with that, I just did it the way I did as it fitted what some
> users needed. Not sure how many people would have a network setup with
> localhost set in dns to point to another machine, Though I agree there is
> no reason why you couldn't do it.
> 
> > > > We have a general approach to non-standard socket names now.
> > >
> > > Great, thats a non problem then, what do you do ?
> >
> > Pick up DEFAULT_PGSOCKET_DIR from config.h.
> 
> Thats ok, but if I was to keep a driver in unixODBC distrib, I would have
> to have a --postgres-socket= option in the config, same problem with
> odbcinst but in reverse. Maybe no simple answer to that one.
> 
> All I do at the moment, is have the driver try the two places it knows
> about, maybe it should be in the ini file, perhaps if the socket_location
> is set it would connect via that. It would fix the problem with using
> localhost to switch the connection method.
> 
> --
> Nick Gorham
> When I die, I want to go like my grandfather did, gently while sleeping,
> and not like his passangers, screaming in a panic, looking for the
> inflatable raft. -- Seen on ./
> 
> 
> 
> 


-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2001-01-24 23:56:06
Subject: Re: Re: [GENERAL] child table doesn't inherit PRIMARY KEY?
Previous:From: Peter EisentrautDate: 2001-01-24 23:42:45
Subject: Re: beta3 Solaris 7 (SPARC) port report [ Was: Looking for . . . ]

pgsql-odbc by date

Next:From: Bruce MomjianDate: 2001-01-25 03:27:07
Subject: Re: ODBC Patch for OJs/Large Querys & Rows
Previous:From: Nick GorhamDate: 2001-01-24 22:37:52
Subject: Re: Re: unixODBC again :-(

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