>but I'll bet
>a nickel your CREATE TYPE says something else --- probably varlena
You win, how can I pay this bet? :)
Very very thanks, I was looking for the error in the wrong place! It was
so simple and works!
But still have another problem, may be related with my output
functions!?!?
>Indeed ... *please* tell us your compiler issued a warning about that.
I did shell scripts that suppress the warnings, so it was a big mistake, I
agree! But I think my problem is not here!
> Well, you oughta allocate result before you store into it, not after,
> and I bet you meant to assign to
tvi_char). Just date
types are allowed!
Any other suggestions??
Thanks!
-Original Message-
From: Jeremy Drake [mailto:[EMAIL PROTECTED]
Sent: segunda-feira, 4 de junho de 2007 00:23
To: Rodrigo Sakai
Cc: PostgreSQL Hackers
Subject: Re: [HACKERS] ERROR: index row size
Just glancing at
Hello,
Ok, I give up! Tried a lot of things in my code! But still get error on
index row size. So, I'm part of my code, if someone could help me! A valid
value for this type is: '(03-jan-2007 , 15-may-2010)'
typedef struct t_periodo
{
DateADT tvi;
DateADT
Hello,
I'm having a big trouble with the index size! I have looked for a solution
in the internet, but the solutions that I found don't fit for me!
I developed a new data type using C and add this new type on PostgreSQL.
Basically, the data type is: (DateADT, DateADT) with some temporal
Hello,
I'm developing an application that needs a different data type. So, I have
implemented this new data type inside postgresql using C, as documentation
shows to.
Basically, the data type is a composition of two timestamps, like:
(timestamp, timestamp) and it is called 'period'. S
Hello,
I have a question about passing parameters to a C function. Imagine the
example by PostgreSQL:
PG_FUNCTION_INFO_V1(complex_add);
Datum
complex_add(PG_FUNCTION_ARGS)
{
Complex*a = (Complex *) PG_GETARG_POINTER(0);
Complex*b = (Complex *) PG_GETARG_P
