On 10/2/06, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> > However, the test right above that means that we'll fail if the user
> > tries something like "row_variable := NULL;":
>
> The patch you seem to have in mind would allow
> row_variable := int_va
Added to TODO under PL/pgSQL:
o Allow row and record variables to be set to NULL constants,
and allow NULL tests on such variables
Because a row is not scalar, do not allow assignment
from NULL-valued scalars.
--
On Tue, Feb 13, 2007 at 05:55:11PM -0500, Bruce Momjian wrote:
>
> Is there a TODO here?
>
> ---
>
> Jim Nasby wrote:
> > On Oct 2, 2006, at 6:28 PM, Tom Lane wrote:
> > > "Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> > >> Ho
Is there a TODO here?
---
Jim Nasby wrote:
> On Oct 2, 2006, at 6:28 PM, Tom Lane wrote:
> > "Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> >> However, the test right above that means that we'll fail if the user
> >> tries som
On Oct 2, 2006, at 6:28 PM, Tom Lane wrote:
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
However, the test right above that means that we'll fail if the user
tries something like "row_variable := NULL;":
The patch you seem to have in mind would allow
row_variable := int_variable;
to succ
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> However, the test right above that means that we'll fail if the user
> tries something like "row_variable := NULL;":
The patch you seem to have in mind would allow
row_variable := int_variable;
to succeed if the int_variable chanced to contain N
I'm looking at how NULLs are handled in relation to plpgsql row types.
Looking at exec_assign_value, it appears that we're supposed to be able
to handle setting a row variable to NULL:
if (*isNull)
{
/* If source is null, just assign nulls to the
