On Mon, 2006-01-09 at 20:23 +0100, Thomas Hallgren wrote:
> Should I consider this as something to add to the PL/Java TODO list?
Probably, yes (if/when I fix the in-tree PLs I was planning to take a
look at all the externally-maintained ones, although you're welcome to
do it instead).
Before doma
Thomas Hallgren <[EMAIL PROTECTED]> writes:
>> Neil Conway <[EMAIL PROTECTED]> writes:
>>> For #2, I'm not sure where the right place to check domain constraints
>>> is.
> Should I consider this as something to add to the PL/Java TODO list?
Yup, probably.
regards, tom la
Tom Lane wrote:
Neil Conway <[EMAIL PROTECTED]> writes:
For #2, I'm not sure where the right place to check domain constraints
is. I was thinking about adding the check to the fmgr function call
logic[1], but the domain checking code needs an ExprContext in which to
evaluate the constraint, wh
Neil Conway <[EMAIL PROTECTED]> writes:
> For #2, I'm not sure where the right place to check domain constraints
> is. I was thinking about adding the check to the fmgr function call
> logic[1], but the domain checking code needs an ExprContext in which to
> evaluate the constraint, which wouldn
I'd like to take a look at fixing the fact that procedural languages do
not check the constraints associated with domain types. I think there
are two separate issues:
(1) In PL/PgSQL, we need to check domain constraints whenever we assign
a new value to a variable of a domain type.
(2) When
