From: | Zeugswetter Andreas <andreas(dot)zeugswetter(at)telecom(dot)at> |
---|---|
To: | "docs(at)postgreSQL(dot)org" <docs(at)postgreSQL(dot)org>, "hackers(at)postgreSQL(dot)org" <hackers(at)postgreSQL(dot)org> |
Subject: | AW: [HACKERS] Reference Guide (binary cursor) |
Date: | 1998-03-27 10:02:33 |
Message-ID: | 01BD596F.D99B08A0@pc9358.sd.spardat.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> My question is:
> I can't see any difference between BINARY and normal cursors.
> Does it works ?
>
> Thanks, Jose'
Yes, this works. The difference is, that for a binary cursor, the column values are not
passed through the type output function. You therefore get the internal representation for a type.
The internal representation is Platform specific, so pay attention when you use a binary cursor
on client x running on hardware y from vendor z accessing a server on hardware a from vendor b.
e.g. for an integer column, you get a C integer number using a binary cursor, whilst you get a
string value like '12345' using the non binary cursor.
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Ulrich Voss | 1998-03-27 10:34:15 | Reminder: Indices are not used |
Previous Message | Michael Meskes | 1998-03-27 08:34:05 | Another parsing problem |