From: schabi at logix-tt.com (Markus Schaber) Date: Thu, 28 Sep 2006 16:50:19 +0200 Subject: [Pljava-dev] VarLenTuple example code In-Reply-To: <451BDB5E.1020107@tada.se> References: <451BD0B1.8000408@logix-tt.com> <451BD2F4.60202@tada.se> <451BD650.2080201@logix-tt.com> <451BDB5E.1020107@tada.se> Message-ID: <451BE12B.6060809@logix-tt.com> Hi, Thomas, Thomas Hallgren wrote: > No, in that case you must have misunderstood. When you do that, you > remove the middleman that sets up the correct SQLData semantics. The > send/receive functions in PostgreSQL maps to the readSQL/writeSQL > methods in SQLData. The readSQL is the method that supposedly populate > your VarLenTuple from the byte buffer native presentation (wrapped in > the SQLInput). The writeSQL creates the native presentation byte buffer > (wrapped in the SQLOutput) from the VarLenTuple. There's absolutely no > need for you to create some other send/receive mechanism in Java. I just re-read your last mail, and I now see that I misread it. But I still don't grasp how the SQLData implementation (readSQL/ writeSQL) knows whether it's supposed to read or write the internal on-disk representation (type C) or the external binary (type B) format? Do I need three different SQLData implementations, one for send (read C, write B), one for receiving (read B, write C), and one for the type mapping (read C, write C)? And which of them are supposed to have the toString()/parse() methods? Anyhow, I'm going to re-read our discussion and the source tomorrow, maybe a little more sleep helps. :-) Thanks, Markus -- Markus Schaber | Logical Tracking&Tracing International AG Dipl. Inf. | Software Development GIS Fight against software patents in Europe! www.ffii.org www.nosoftwarepatents.org -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 252 bytes Desc: OpenPGP digital signature URL: