On Mon, 2011-06-27 at 12:16 +0200, Florian Pflug wrote:
> I wouldn't take it that far. What I had in mind was to *only* support
> the case where the cast directly follows the function call, i.e. the case
> f(...)::type
OK, so instead of writing:
range(lower(range(1,2)),upper(range(1,2)))::int8range
users would write:
range(lower(range(1,2)::int8range),upper(range(1,2)::int8range))::int8range
A little more verbose, but it seems like it wouldn't be a practical
problem in very many cases. Multiple levels of constructors seem like
they'd be fairly uncommon, and probably a case where a function should
be written anyway.
OK, I'll have to think about this a little more, but it seems like a
reasonable approach.
Regards,
Jeff Davis
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
