Thanks, Tom. It is done by modifying coerce_type() and
can_coerce_type(). The reason I have to keep to verson 7.3 is I am
working on a research prototype that is built over pgsql 7.3. I need
the extra functions provided by that prototype.
On 1/25/06, Tom Lane <[EMAIL PROTECTED]> wrote:
> andrew <
andrew <[EMAIL PROTECTED]> writes:
> Sorry, I modified the parser code and forgot abt it. Now there is no
> problem in creating the function. But there is another problem. I
> create a function to accept record type parameter. But when I call it
> on a specific composite type, error is reported. Th
sorry, mistakenly leave out another try:
backend> select *, complete(CAST (Person AS record)) from Person
QUERY: select *, complete(CAST (Person AS record)) from Person
ERROR: Relation reference "person" cannot be used in an expression
On 1/25/06, andrew <[EMAIL PROTECTED]> wrote:
> Sorry, I mo
Sorry, I modified the parser code and forgot abt it. Now there is no
problem in creating the function. But there is another problem. I
create a function to accept record type parameter. But when I call it
on a specific composite type, error is reported. The followings are
what I have done:
backend
andrew <[EMAIL PROTECTED]> writes:
> ERROR: parser: parse error at or near "record" at character 21
> in Warn_restart code
> What is the problem here? Did you test it on 7.3?
Yeah, 7.3.13 to be exact. (There have been a couple of changes in the
parser in the 7.3 branch, according to the CVS log
The following is just copied from the screen.
backend> create function foo(record) returns int4 as '$libdir/bar' language C
QUERY: create function foo(record) returns int4 as '$libdir/bar' language C
ERROR: parser: parse error at or near "record" at character 21
in Warn_restart code
What is the
andrew <[EMAIL PROTECTED]> writes:
> I use 7.3 and use RECORD as the input data type of the function by
> "create function foo(record) returns int4 as '$libdir/bar' language
> C". But I got this error msg:" ERROR: parser: parse error at or near
> "record" at character". What is the problem?
Sur
I use 7.3 and use RECORD as the input data type of the function by
"create function foo(record) returns int4 as '$libdir/bar' language
C". But I got this error msg:" ERROR: parser: parse error at or near
"record" at character". What is the problem? I look up the 7.3
manual. it seems record is a
On Tue, 2006-01-24 at 14:38, Tom Lane wrote:
> Yl Zhou <[EMAIL PROTECTED]> writes:
> > But I have to use 7.3 due to some limitations. Can I do it in 7.3?
>
> Probably, but I forget how (and I can guarantee that it will break
> when you do move to 8.0 or later, because we changed the internal
> rep
Yl Zhou <[EMAIL PROTECTED]> writes:
> But I have to use 7.3 due to some limitations. Can I do it in 7.3?
Probably, but I forget how (and I can guarantee that it will break
when you do move to 8.0 or later, because we changed the internal
representation of rowtype arguments). You'd be *much* bette
Can anyone tell me whether 7.3 supports unspecified record types or not?
On 1/24/06, Tom Lane <[EMAIL PROTECTED]> wrote:
Yl Zhou <[EMAIL PROTECTED]> writes:> Do you mean this function? Seems I cannot get much information from it...That would appear to be Postgres 7.3 :-(
You need a considerably ne
For what it's worth, the next release of PL/Java has support for both RECORD parameters and
SETOF RECORD return types. The adventurous can try out the current CVS HEAD.
Regards,
Thomas Hallgren
Tom Lane wrote:
Yl Zhou <[EMAIL PROTECTED]> writes:
I want to implement a UDF that can accept a par
But I have to use 7.3 due to some limitations. Can I do it in 7.3? On 1/24/06, Tom Lane <[EMAIL PROTECTED]> wrote:
Yl Zhou <[EMAIL PROTECTED]> writes:
> Do you mean this function? Seems I cannot get much information from it...That would appear to be Postgres 7.3 :-(You need a considerably newer ver
Yl Zhou <[EMAIL PROTECTED]> writes:
> Do you mean this function? Seems I cannot get much information from it...
That would appear to be Postgres 7.3 :-(
You need a considerably newer version of Postgres if you want to do much
of anything useful with unspecified-type records. 8.0 has most of that
Do you mean this function? Seems I cannot get much information from it.../* * record_out - output routine for pseudo-type RECORD. */Datumrecord_out(PG_FUNCTION_ARGS){ elog(ERROR, "Cannot display a value of type %s", "RECORD");
PG_RETURN_VOID(); /* keep compiler quiet */}On
Richard Huxton writes:
> Tom Lane wrote:
>> You could do that in C, but none of the available PLs support it.
> How would you define the signature for the function? One parameter of
> type anyelement?
Type RECORD would be a better choice --- ANYELEMENT allows scalar types
which is not what you
Tom Lane wrote:
Yl Zhou <[EMAIL PROTECTED]> writes:
I want to implement a UDF that can accept a parameter which is a tuple of
any table, and returns the number of NULL attributes in this tuple.
Different tables may have different schemas. How can I implement this
function? Thanks.
You could d
check
http://archives.postgresql.org/pgsql-novice/2005-02/msg00227.php
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
Yl Zhou <[EMAIL PROTECTED]> writes:
> I want to implement a UDF that can accept a parameter which is a tuple of
> any table, and returns the number of NULL attributes in this tuple.
> Different tables may have different schemas. How can I implement this
> function? Thanks.
You could do that in C,
I want to implement a UDF that can accept a parameter which is a tuple of any table, and returns the number of NULL attributes in this tuple. Different tables may have different schemas. How can I implement this function? Thanks.
andrew
Test: (my DATESTYLE is set to European)
select test('30/01/1972'::date);
result -> '01-12-1971'
-Message d'origine-
De : Moray McConnachie <[EMAIL PROTECTED]>
À : [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date : samedi 16 octobre 1999 01:06
Objet : [GEN
hi...
>
> > CREATE FUNCTION startofregyear(date) RETURNS date AS '
> > SELECT text_datetime(''01/12/''
> float8_text(datepart(''year'',$1)-1))
> > AS answer;
> > ' LANGUAGE 'SQL';
>
> absolutely not, I tried that already.
> I get "attribute not found" error wherever the opening double-quot
Hi
On postgresql 6.4.2 running on digital unix 4.0d. This bit of code
- pfunc.c---
/*
cc -c -I/usr/local/pgsql/include pfunc.c
ld -shared -expect_unresolved '*' -o pfunc.so pfunc.o
cc -o pfunc -I/usr/local/pgsql/include pfunc.c
create function int10() returns int4 as '/p
23 matches
Mail list logo
