X-Original-To: pgsql-php-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 07CE29DCAC2 for ; Fri, 3 Feb 2006 04:41:34 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 41445-04 for ; Fri, 3 Feb 2006 04:41:34 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.194]) by postgresql.org (Postfix) with ESMTP id 0268E9DCA0D for ; Fri, 3 Feb 2006 04:41:31 -0400 (AST) Received: by xproxy.gmail.com with SMTP id s14so396541wxc for ; Fri, 03 Feb 2006 00:41:33 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=hjIE5U6M2ghuRbftLxTQ9hieti2lYym1YZcd803TuC8nLuj5uXel/YMkrrspmlCmxnWl5JcZEsHOYemgXsQyegUZTT3qbBWrt7IY9Zfi2dapyLQgT0lYG7v2uLibbj7MGAydz43Qwl7cxCepJBIprE/nV2Al3Ca2IhBfxc8Ddoc= Received: by 10.70.130.8 with SMTP id c8mr1808543wxd; Fri, 03 Feb 2006 00:41:33 -0800 (PST) Received: by 10.70.7.16 with HTTP; Fri, 3 Feb 2006 00:41:33 -0800 (PST) Message-ID: Date: Fri, 3 Feb 2006 03:41:33 -0500 From: Patrick White To: pgsql-php@postgresql.org Subject: Re: php and postgresql on windows In-Reply-To: <4cb3dbb70602022321o4adbcd9ek@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <4cb3dbb70602022103l57309b98l@mail.gmail.com> <20060203051943.038479DCBEE@postgresql.org> <4cb3dbb70602022321o4adbcd9ek@mail.gmail.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.12 required=5 tests=[AWL=0.120] X-Spam-Score: 0.12 X-Spam-Level: X-Archive-Number: 200602/7 X-Sequence-Number: 3423 I had some similar problems getting the postgre library to become available to PHP. The issue I was having was that I didn't realise the order of which the server will look for the php.ini file (I thought it was simply looking in the PATH directories), such as the list I will provide for future reference: 1.PHPIniDir directive (Apache 2 module only) 2.HKEY_LOCAL_MACHINE\SOFTWARE\PHP\IniFilePath 3. The PHPRC environment variable 4. Directory of PHP (for CLI), or the web server's directory (for SAPI modules) 5. Windows directory (C:\windows or C:\winnt) My problem was that Apache was set to look in a directory that contained a completly default php.ini file. On 2/3/06, Przemek Kowalczyk wrote: > On 03/02/06, Randy Moller wrote: > > Actually, the php_pgsql.dll file does NOT natively install on the windo= ws > > CGI distribution. If you installed using the "installer", then download= the > > zip distribution and extract the dll from the ext folder. > > > > Next, if you haven't already done so, uncomment the extension line on > > php.ini, and you should be good to go. > > > > If you installed originally from the zip/tar/rar file, then it should b= e > > there, yes. > > > > Hope this helps. > It does not work. Does it matter if I install it as cgi binary or > apache module? I tried both. The php.ini files get read because I can > see the extension_dir changing for example. > I tried uncommenting the mysql dll in php.ini for fun and and I don't > see anything about mysql in phpinfo.php > Could this be because my drive is F instead of c? No that's stupid eh? > > ---------------------------(end of broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match >