"Tom Dunstan" <[EMAIL PROTECTED]> writes:
> I wouldn't get too worried, though. These are defensive error messages
> that are really just checking for sane input, and they seem difficult
> to deliberately trip, let alone accidentally, so stressing about them
> is probably unnecessary.
Right. I'm
On Nov 28, 2007 11:01 AM, Tom Lane <[EMAIL PROTECTED]> wrote:
> > What is an actual enum type? And how should a user react if he got this
> > message? I would ask, "why not?".
>
> Yeah, I would too, but without a concrete example to look at it's hard
> to say if the situation could be improved.
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> There are a few error messages like this in the code:
> /*
> * We rely on being able to get the specific enum type from the
> calling
> * expression tree. The generic type mechanism should have ensured
> that
> * b
There are a few error messages like this in the code:
/*
* We rely on being able to get the specific enum type from the calling
* expression tree. The generic type mechanism should have ensured that
* both are of the same type.
*/
enumtypoid = g
