Problem with stored procedure

This is a multi-part message in MIME format.
--------------020000040409060302000000
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hello,

In this example, I use 2 tables :
create table types (
typnum integer primary key,
catcode varchar(2),
typlib varchar(35));

create table uv (
uvnum varchar(5) primary key,
typnum integer,
uvlib varchar(50));

alter table uv
add constraint fk_uv_type foreign key (typnum)
references types (typnum)
on delete restrict on update restrict;

I also use stored procedures :

create function numtype(varchar) returns integer as '
declare
codetype alias for $1;
coderet integer;
begin
select into coderet typnum from types
where typcode = codetype and catcode = ''UV'';
return coderet;
end;
' language 'plpgsql';

create function insert_uv(varchar,varchar,varchar) returns integer as '
declare
codeuv alias for $1;
codetype alias for $2;
libuv alias for $3;
cletype integer;
begin
select into cletype numtype(codeuv);
insert into uv values (codeuv, cletype, libuv);
return cletype;
end;
' language 'plpgsql';

When I do :

select insert_uv('SGBD','DUVC','TEST BD');
I get the following message :
ERROR: insert or update on table "uv" violates foreign key constraint
"fk_uv_caracteri_type"
DETAIL: Key (typnum)=(43) is not present in table "types".

I don't kown why.

Anyone has an idea ?

With best regards,
Patrice

--------------020000040409060302000000
Content-Type: text/x-vcard; charset=utf-8;
name="oliverp21.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="oliverp21.vcf"

begin:vcard
fn:Patrice OLIVER
n:OLIVER;Patrice
email;internet:oliverp21@free.fr
x-mozilla-html:FALSE
version:2.1
end:vcard


--------------020000040409060302000000
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0


---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

--------------020000040409060302000000--

Re: Problem with stored procedure

Patrice OLIVER wrote:
[snip]
> create function insert_uv(varchar,varchar,varchar) returns integer as '
> declare
> codeuv alias for $1;
> codetype alias for $2;
> libuv alias for $3;
> cletype integer;
> begin
> select into cletype numtype(codeuv);
> insert into uv values (codeuv, cletype, libuv);
> return cletype;
> end;
> ' language 'plpgsql';
>
> When I do :
>
> select insert_uv('SGBD','DUVC','TEST BD');
> I get the following message :
> ERROR: insert or update on table "uv" violates foreign key constraint
> "fk_uv_caracteri_type"
> DETAIL: Key (typnum)=(43) is not present in table "types".
>
> I don't kown why.

Before your "insert into" add:
RAISE NOTICE ''cletype = %'', cletype;

This will show what value cletype has. Presumably it's 43 and you don't
have an equivalent row in "types".

Or have I misunderstood the problem?

--
Richard Huxton
Archonet Ltd

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

Re: Problem with stored procedure

Patrice OLIVER wrote:

> Hello,
>
> In this example, I use 2 tables :
> create table types (
> typnum integer primary key,
> catcode varchar(2),
> typlib varchar(35));
>
> create table uv (
> uvnum varchar(5) primary key,
> typnum integer,
> uvlib varchar(50));
>
> alter table uv
> add constraint fk_uv_type foreign key (typnum)
> references types (typnum)
> on delete restrict on update restrict;
>
> I also use stored procedures :
>
> create function numtype(varchar) returns integer as '
> declare
> codetype alias for $1;
> coderet integer;
> begin
> select into coderet typnum from types
> where typcode = codetype and catcode = ''UV'';

why not -> select *typenum* into coderet from types
where typcode = codetype and catcode = ''UV'';

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly