-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160
> Perhaps have quote_nullable() then as well? > > You then use quote_nullable() in INSERT and UPDATE SET clauses and > quote_literal() in SELECT WHERE clauses. I still don't see the use case. Wouldn't your app still need to check for nullability anyway, to avoid " = NULL"? (Aside: seems to me that SET foo = NULL; really should be SET foo TO NULL; to be consistent with WHERE foo IS NULL;) - -- Greg Sabino Mullane [EMAIL PROTECTED] PGP Key: 0x14964AC8 200710101221 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iD8DBQFHDPwyvJuQZxSWSsgRAwGaAJ92ICR+MyclkmWvJRkC4vazIw+b0ACghpZt WXbCxe0abFlp8jwr0ol/fac= =oWqD -----END PGP SIGNATURE----- ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
