From: | Thomas Hallgren <thhal(at)mailblocks(dot)com> |
---|---|
To: | Markus Schaber <schabios(at)logi-track(dot)com> |
Cc: | "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org>, Filip Hrbek <filip(dot)hrbek(at)plz(dot)comstar(dot)cz> |
Subject: | Re: PLJava and Database Meta Data |
Date: | 2005-02-11 13:19:33 |
Message-ID: | thhal-0aEnoAuNMxicXo3uf6+PCZQjtO2fifP@mailblocks.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Markus Schaber wrote:
>Okay, so this is fine for primitive types. How does SPI deal with
>complex types?
>
>
A complex type is represented by a C-structure called HeapTuple. A
HeapTuple is associated with a TupleDesc that acts as its description.
The HeapTuple is passed by reference (a C-language pointer) and PLJava
will obtains its individual values as Datums using a function called
SPI_getbinval. An individual value may of course be a reference to
another complex type.
Complex types are created using the function heap_form_tuple.
>Yes, I have. Especially for large geometries. In our database, we have
>geometry objects up to 20MB per piece. Also, in PostGIS, send/receive
>binary representation differs slightly from internal representation (and
>input/output text is even more overhead).
>
>
Ok. We are probably talking about different things. I'm referring to the
internal C-functions that are executed directly in the backend.
- thomas
From | Date | Subject | |
---|---|---|---|
Next Message | Markus Schaber | 2005-02-11 13:40:47 | Re: PLJava and Database Meta Data |
Previous Message | Markus Schaber | 2005-02-11 12:54:50 | Re: PLJava and Database Meta Data |