Tom Lane writes:
> Perhaps there's a case for prohibiting volatile casts (as opposed to
> stable ones), but I don't really see it. I'd prefer to just remove
> this restriction. Comments?
I'm not wedded to it, I just modelled it after the SQL standard, but
evidently the volatility levels are different in detail. I would disallow
volatile casts in any case. There ought to be a minimal behavioral
contract between creators and users of types.
--
Peter Eisentraut peter_e@gmx.net