Given:
CREATE DOMAIN int_array AS int[];
The operator [] works fine in 4.1beta1:
SELECT (ARRAY[1,2,3]::int_array)[1];
proving that int_array is an array type with element type int.
It is inconsistent that other array functions and operators don't work.
On Mon, 2011-05-09 at 23:32 -0400, T
The documentation for the Server Programming Interface
is underspecified such that it is impossible to create
real extensions using only the documented interface.
For example, in the example 43.5
http://www.postgresql.org/docs/9.1/static/spi-examples.html
a variable of type SPITupleTable is being
E.1.2.2. Casting
* Tighten casting checks for domains based on arrays (Tom Lane)
When a domain is based on an array type,..., such a domain type
is no longer allowed to match an anyarray parameter of a
polymorphic function, except by explicitly down
PostgreSQL's XML is in great shape by then, but we'll see!
PostgreSQL is a great tool and y'all are doing great work in maintaining
and improving it. The community has also been very helpful since I got
over my shyness about asking for help.
_Greg
J. Greg Davidson
Ancient Mariner
sideration,
_Greg
J. Greg Davidson
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ts of specializations of it). Is there an efficient (and maybe
even easy) way to legally convert such arrays?
Thanks for any suggestions you may have,
_Greg
J. Greg Davidson
P.S. If you want a more complete example to refer to, here it is:
CREATE TYPE base_refs;
CREATE OR REPLACE
FUNCTION base_r
Dear PostgreSQL Hackers,
Through PostgreSQL 8.3, both of the following functions worked, using
generate_series(array_lower($1, 1), array_upper($1, 1)) i
instead of generate_subscripts($1, 1).
With PostgreSQL 8.4, both are accepted, but only the second one works,
regardless of whether I use gene
Hi Josh,
I think that any special "features" common to all on system tables would
go nicely near the top of 44.1 "System Catalogs Overview". That plus a
specific error message, not just a "PERMISSION DENIED", so that someone
like me can put the error message in the PostgreSQL.org search box to
fi
e allowed.
BTW, I'm loving most of what I see in 8.4,
_Greg
J. Greg Davidson
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
