postgresql/src/backend/utils/adt
Tom Lane 304845075c Use array_contains_nulls instead of ARR_HASNULL on user-supplied arrays.
This applies the fix for bug #5784 to remaining places where we wish
to reject nulls in user-supplied arrays.  In all these places, there's
no reason not to allow a null bitmap to be present, so long as none of
the current elements are actually null.

I did not change some other places where we are looking at system catalog
entries or aggregate transition values, as the presence of a null bitmap
in such an array would be suspicious.
2011-01-09 13:09:07 -05:00
..
acl.c
array_userfuncs.c
arrayfuncs.c Use array_contains_nulls instead of ARR_HASNULL on user-supplied arrays. 2011-01-09 13:09:07 -05:00
arrayutils.c Use array_contains_nulls instead of ARR_HASNULL on user-supplied arrays. 2011-01-09 13:09:07 -05:00
ascii.c
bool.c
cash.c
char.c
date.c
datetime.c
datum.c
dbsize.c
domains.c
encode.c
enum.c
float.c
format_type.c
formatting.c
genfile.c
geo_ops.c
geo_selfuncs.c
inet_cidr_ntop.c
inet_net_pton.c
int8.c
int.c
like_match.c
like.c
lockfuncs.c
mac.c
Makefile
misc.c
nabstime.c
name.c
network.c
numeric.c
numutils.c
oid.c
oracle_compat.c
pg_locale.c
pg_lzcompress.c
pgstatfuncs.c
pseudotypes.c
quote.c
regexp.c
regproc.c
ri_triggers.c
rowtypes.c
ruleutils.c
selfuncs.c
tid.c
timestamp.c
trigfuncs.c
tsginidx.c
tsgistidx.c
tsquery_cleanup.c
tsquery_gist.c
tsquery_op.c
tsquery_rewrite.c
tsquery_util.c
tsquery.c
tsrank.c Use array_contains_nulls instead of ARR_HASNULL on user-supplied arrays. 2011-01-09 13:09:07 -05:00
tsvector_op.c
tsvector_parser.c
tsvector.c
txid.c
uuid.c
varbit.c
varchar.c
varlena.c
version.c
windowfuncs.c
xid.c
xml.c