Re: No error message set after executing a simple SELECT statement twice

--Iovxle6z3WGVZjcj
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

> If anyone sees this, it's because the postgres DBD object went out of
> scope and was disconnected underneath me (the script forks).
>=20
> The fix was to simply use the "InactiveDestory =3D> 1" as an option at
> the time of dbconnect() as per the doc. Wow, that was painful.

Glad it got solved! I didn't reply as I couldn't figure out what was=20
going on, but in retrospect forking is always a good suspect for=20
mysterious DBI issues (similar to the way SELinux is for=20
mysterious Linux issues :)

--=20
Greg Sabino Mullane [email protected]
End Point Corporation
PGP Key: 0x14964AC8

--Iovxle6z3WGVZjcj
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAlayj7UACgkQvJuQZxSWSsgZzACeOowk2zEJO/yM/JfmPCAgcfYq
rUMAmgMzYdcc+JlxzP12/sJaseyWOfM0
=v5R4
-----END PGP SIGNATURE-----

--Iovxle6z3WGVZjcj--