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   [EMAIL PROTECTED]


---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly

Reply via email to