| From: | Dmitriy Agafonov <Dmitriy(dot)Agafonov(at)msdw(dot)com> | 
|---|---|
| To: | pgsql-general(at)postgresql(dot)org | 
| Subject: | cursor name : uniqueness scope | 
| Date: | 2000-11-06 19:43:17 | 
| Message-ID: | 3A0709D5.FC68EABF@msdw.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general | 
Stupid question - what's the uniqueness scope of a cursor name. Is it
connection (as, I assume, it's supposed to be) or is it something else
(database, server, client, ...) ?  I am accessing the database using C
API thru a set of C++ wrappers, which I wrote myself (the standard ones
weren't satisfactory) and I am currently retrieving the stringified
data, which I convert to a particular datatype using sscanf. I'd like to
improve the performance of my application by retrieving the binary data
directly.  AFAIK the only way to do that is by using a binary cursor (is
it gonna change in 7.1, by the way?). I don't want to specify the cursor
name explicitely every time I need to do a select. Instead I'm going to
use a simple name generator. I just need to know what it is supposed to
be associated with - a connection, client, database...
Thank you,
Dmitriy Agafonov.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Mercer | 2000-11-06 19:45:39 | permissions on databases vs. permissions on tables | 
| Previous Message | joe | 2000-11-06 18:59:14 | Synchronizing Data? |