From: | "James Harper" <james(dot)harper(at)bendigoit(dot)com(dot)au> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | libpq questions |
Date: | 2006-01-31 11:23:54 |
Message-ID: | AEC6C66638C05B468B556EA548C1A77DAF067F@trantor |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
For the libpq interface:
I need to be able to know if a column in a result from a query is
nullable or not. From reading the documentation it seems that I can
obtain the following information:
. scan all the rows in the result and see if there exists a null value
for each column...
. backtrack the column to the source table (assuming a non-calculated
field) and check the nullable status there
Neither of the above is particularly cheap to do...
Which leads me to my next question... If I executed a select against a
table with a million rows, and the query returned all of the rows, what
happens? Are all the rows read into memory on the client before
returning the result? Or are rows only fetched from the server as
required?
Thanks
James
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Hallgren | 2006-01-31 11:51:25 | Re: New project launched : PostgreSQL GUI |
Previous Message | Howard Cole | 2006-01-31 11:11:58 | Re: How to enumerate/drop user sessions in windows |