From: | JanWieck(at)t-online(dot)de (Jan Wieck) |
---|---|
To: | Looc TREGOUKT <loic(at)cri74(dot)org> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: insert new type (object ?) |
Date: | 2000-05-02 14:11:45 |
Message-ID: | 200005021411.QAA19485@hot.jw.home |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Looc TREGOUKT wrote:
> I've ever ask my question (differently) in the other lists but no
> response , so i think you are my last chance ....
>
> I have the following table in my PostgreSQL Database :
>
> create table one ( i int4 , j int4) ;
>
> create table two ( o one , id int4 ) ;
>
> insert into one values (10, 20) ;
>
> create function fct() returns one as '
> select i as i , j as j from one ; '
> language 'sql';
>
> insert into two (select fct() , 1 ) ;
>
> So when i do : select * from two
>
> o i d
> 136801144 1
>
> --------------------------------------------------
> What is the first number ? I 've succeed with insert a new type ( one)
> into my base ?
> But i can't access to the information into o ?
>
> Please , if you have any information about this problem , please contact
> me
IIRC it should be the in memory address of the tuple table
slot returnd by the function fct() at the INSERT time. At
least, nothing useful.
This is definitely broken and for now you should stay away
from functions returning tuples or SETs.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-05-02 14:58:50 | Re: shmem_seq may be a bad idea |
Previous Message | Thomas Lockhart | 2000-05-02 13:40:43 | Re: Patch submission |