-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160
> How do you propose to enforce it given the ability of functions to have > side efects? By rolling back every transaction? Not our problem - it simply calls SET TRANSACTION READ ONLY after every BEGIN. :) (This was a quick little side-effect of me making sure we were testing all of the DBI attributes). We should probably put a link to the relevant PG docs in that area of the POD. - -- Greg Sabino Mullane [EMAIL PROTECTED] End Point Corporation PGP Key: 0x14964AC8 200807262345 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAkiL70UACgkQvJuQZxSWSsju5QCg0LqPqJpQVyTFvyybj4sEHAuQ jeUAoNwIsENNLAw2TnsaKsx0qW+AXIbp =zQLr -----END PGP SIGNATURE-----
