Why doesn"t version 8.0.1 talk to php. Something I"ve done?

This is a multi-part message in MIME format.

------=_NextPart_000_000F_01C54987.CFD93B60
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

I've discovered that version 8.0.1 of postgresql does not, or at least as I
had it configured, talk to php. Backing up to 7.4.7 does. Is the reason that
it simply does not yet, or do I have something wrong in the config. If not
yet, when?

Versions are:
httpd-2.0.54 (apache2)
php-5.0.4
postgresql-8.0.1 (& 7.4.7)

------=_NextPart_000_000F_01C54987.CFD93B60
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable



charset=3Diso-8859-1">

Re: Why doesn"t version 8.0.1 talk to php. Something I"ve done?

On Apr 25, 2005, at 12:13 PM, John Mohr wrote:

> I've discovered that version 8.0.1 of postgresql does not, or at least=20
> as I had it configured, talk to php. Backing up to 7.4.7 does. Is the=20
> reason that it simply does not yet, or do I have something wrong in=20
> the config. If not yet, when?
> =A0
> Versions are:
> httpd-2.0.54 (apache2)
> php-5.0.4
> postgresql-8.0.1 (& 7.4.7)


I'm using 8.0.2 and php 5.0.4 without any problems. What error are you=20
getting? Is 8.0.1 at the exact same path you had for 7.4.7? php -i=20
might provide some clues.


John DeSoi, Ph.D.
http://pgedit.com/
Power Tools for PostgreSQL


---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

Re: Why doesn"t version 8.0.1 talk to php. Something I"ve done?

On Mon, Apr 25, 2005 at 11:13:30AM -0500, John Mohr wrote:
>
> I've discovered that version 8.0.1 of postgresql does not, or at least as I
> had it configured, talk to php. Backing up to 7.4.7 does. Is the reason that
> it simply does not yet, or do I have something wrong in the config. If not
> yet, when?

Please expand on what "does not talk to" means. What are you doing,
what are you expecting to happen, and what actually does happen?
Are you getting an error? If so, what is it? (Please copy and
paste it verbatim, rather than typing what you think it says.) You
might have to tweak your script or your PHP settings to see the
error message, either in the script output or in the web server's
error logs.

--
Michael Fuhr
http://www.fuhr.org/~mfuhr/

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org)

Re: Why doesn"t version 8.0.1 talk to php. Something I"ve

--Signature=_Mon__25_Apr_2005_20_57_23_+0200_bJ=sNat8ZKyAwyO S
Content-Type: text/plain; charset=ISO-8859-15
Content-Disposition: inline
Content-Transfer-Encoding: base64

T24gTW9uLCAyNSBBcHIgMjAwNSAxMToxMzozMCAtMDUwMCAiSm9obiBNb2hy Ig0KPGp0bW9ockBo
ZWFsdGhjb25yZXNvdXJjZXMuY29tPiB0aG91Z2h0IGxvbmcsIHRoZW4gc2F0 IGRvd24gYW5kIHdy
b3RlOg0KDQo+IEkndmUgZGlzY292ZXJlZCB0aGF0IHZlcnNpb24gOC4wLjEg b2YgcG9zdGdyZXNx
bCBkb2VzIG5vdCwgb3IgYXQgbGVhc3QNCj4gYXMgSSBoYWQgaXQgY29uZmln dXJlZCwgdGFsayB0
byBwaHAuIEJhY2tpbmcgdXAgdG8gNy40LjcgZG9lcy4gSXMgdGhlDQo+IHJl YXNvbiB0aGF0IGl0
IHNpbXBseSBkb2VzIG5vdCB5ZXQsIG9yIGRvIEkgaGF2ZSBzb21ldGhpbmcg d3JvbmcgaW4NCj4g
dGhlIGNvbmZpZy4gSWYgbm90IHlldCwgd2hlbj8NCj4gDQo+IFZlcnNpb25z IGFyZToNCj4gaHR0
cGQtMi4wLjU0IChhcGFjaGUyKQ0KPiBwaHAtNS4wLjQNCj4gcG9zdGdyZXNx bC04LjAuMSAoJiA3
LjQuNykNCj4gDQoNCkRpZCB5b3UgYWN0aXZhdGUgVENQL0lQIGNvbm5lY3Rp b25zPyBJbiBwb3N0
Z3Jlc3FsLmNvbmY6DQoNCiMtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQojIENPTk5FQ1RJT05T IEFORCBBVVRIRU5U
SUNBVElPTg0KIy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCg0KIyAtIENvbm5lY3Rpb24gU2V0 dGluZ3MgLQ0KDQps
aXN0ZW5fYWRkcmVzc2VzID0gJyonICAjIHdoYXQgSVAgaW50ZXJmYWNlKHMp IHRvIGxpc3RlbiBv
bjsgDQogICAgICAgICAgICAgICAgICAgICAgICAjIGRlZmF1bHRzIHRvIGxv Y2FsaG9zdCwgJyon
ID0gYW55DQoNCg0KU3ludGF4IGRpZmZlcnMgYmV0d2VlbiBlYXJsaWVyIHJl bGVhc2VzIGFuZCA4
LnguDQoNClJlZ2FyZHMsDQotLSANCkZyYW5rIEZpbm5lcg0KDQpJbnZlbml1 cyAtIEz2c3VuZ2Vu
IG1pdCBMaW51eA0KS/ZwZmNoZW5zdHJh32UgMzYNCjU3MDcyIFNpZWdlbg0K VGVsZWZvbjogMDI3
MSAyMzEgODYwNiAgICBNYWlsOiBmcmFuay5maW5uZXJAaW52ZW5pdXMuZGUN ClRlbGVmYXg6IDAy
NzEgMjMxIDg2MDggICAgV2ViOiAgaHR0cDovL3d3dy5pbnZlbml1cy5kZQ0K S2V5IGZpbmdlcnBy
aW50ID0gOTBERiBGRjQwIDU4MkUgNkQ2QiBCQURGICA2RTZBIEE3NEUgNjdF NCBFNzg4IDI2NTEN
Cg0K

--Signature=_Mon__25_Apr_2005_20_57_23_+0200_bJ=sNat8ZKyAwyO S
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFCbT2a9yTJ83o5N2cRAgHfAKDZvQ/ArrTF7Bm4BPUjeI2+ppZDiACb B403
DmMz/WAvhCx4NIfSLMhG/xY=
=wK/3
-----END PGP SIGNATURE-----

--Signature=_Mon__25_Apr_2005_20_57_23_+0200_bJ=sNat8ZKyAwyO S--