Re: doubt about datum

From: Luca Ferrari
Subject: Re: doubt about datum
Date: ,
Msg-id: 200707310907.56878.fluca1978@infinito.it
(view: Whole thread, Raw)
In response to: Re: doubt about datum  (Tom Lane)
List: pgsql-novice

Tree view

doubt about datum  (Luca Ferrari, )
 Re: doubt about datum  (Tom Lane, )
  Re: doubt about datum  (Luca Ferrari, )
  Re: doubt about datum  (Luca Ferrari, )
   Re: doubt about datum  (Tom Lane, )

On Tuesday 31 July 2007 your cat, walking on the keyboard, wrote:
> Luca Ferrari <> writes:
> > I'm new to postgresql programming and I'd like to understand what a datum
> > is
>
> A value of any data type -- which particular type is not said by the
> datum itself, but we always have context information to tell us that.

Not sure to get this. With "any data type" you mean user defined types or also
internal data types? I guess the former. And what do you mean by "context"? I
noticed that Datum is used as return type in the function v1 convention, thus
I guess the context is related to the function itself, which return type is
know by the SQL side. Is this what you mean?


>
> > Moreover why it does not need transaction
> > visibility as an ordinary tuple (xmin, cmin, cmax, xmax)?
>
> Datums are values.  '42'::int does not need visibility information;
> its value is always the same.


Even more confused here! In the case of function returns values I agree that
there is no needing for transaction information, since the value should be
evaluated on the fly, right? Maybe what I'm not getting is about a tuple that
includes both internal values and a datum: is that possibile? Because in this
case how is the tuple header handled (since datum header should overlap the
transaction header xmin,xmax...). Sorry if my question is too trivial.

Thanks,
Luca



pgsql-novice by date:

From: Oliver Elphick
Date:
Subject: Re: tsearch2.sql and different versions of PostgreSQL
From: Michael Fuhr
Date:
Subject: Re: SQL_CALC_FOUND_ROWS equivalent in PostgreSQL