postgresql/contrib/ltree
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
..
data
expected
sql
_ltree_gist.c Use array_contains_nulls instead of ARR_HASNULL on user-supplied arrays. 2011-01-09 13:09:07 -05:00
_ltree_op.c Use array_contains_nulls instead of ARR_HASNULL on user-supplied arrays. 2011-01-09 13:09:07 -05:00
.gitignore
crc32.c
crc32.h
lquery_op.c Use array_contains_nulls instead of ARR_HASNULL on user-supplied arrays. 2011-01-09 13:09:07 -05:00
ltree_gist.c Use array_contains_nulls instead of ARR_HASNULL on user-supplied arrays. 2011-01-09 13:09:07 -05:00
ltree_io.c
ltree_op.c Use memcmp() rather than strncmp() when shorter string length is known. 2010-12-21 22:11:40 -05:00
ltree.h
ltree.sql.in Remove useless whitespace at end of lines 2010-11-23 22:34:55 +02:00
ltreetest.sql
ltxtquery_io.c Fix erroneous parsing of tsquery input "... & !(subexpression) | ..." 2010-12-19 12:48:34 -05:00
ltxtquery_op.c
Makefile
uninstall_ltree.sql Remove useless whitespace at end of lines 2010-11-23 22:34:55 +02:00