Re: Calling function from VFP changes character field to Memo - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Calling function from VFP changes character field to Memo
Date
Msg-id a94158a9-ff24-9a15-51f7-af265d052f90@aklaver.com
Whole thread Raw
In response to Re: Calling function from VFP changes character field to Memo  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On 11/15/22 10:44 AM, Tom Lane wrote:
> Frank Cazabon <frank.cazabon@gmail.com> writes:

> 
>> Any idea what I need to do to get it to return the character(30) type?
> 
> There's no chance of getting back the "30" part with this structure,
> because function signatures do not carry length restrictions.
> What I expect is happening is that you get firstname as an
> unspecified-length "character" type, and something on the client
> side is deciding to cope with that by calling it "Memo" instead.

My experience is that frameworks 'see' ::text as Memo/Textarea and 
::char/varchar as Input.

> 
> You could perhaps work around that by defining a named composite
> type:
> 
> create type testfunction_result as (firstname character(30), ...);
> 
> create function testfunction() returns setof testfunction_result as ...
> 
>             regards, tom lane
> 
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com



pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Calling function from VFP changes character field to Memo
Next
From: Frank Cazabon
Date:
Subject: Re: Calling function from VFP changes character field to Memo