Skip site navigation (1) Skip section navigation (2)

Re: modifying in the libpg files

From: "Islam Hegazy" <islheg(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-interfaces(at)postgresql(dot)org>
Subject: Re: modifying in the libpg files
Date: 2007-04-22 03:59:33
Message-ID: 003e01c78492$a69dce80$ (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
But can you tell me how to let depend on the shared library of 
PrintQueryTuples? I need to implement this to show my boss that this final 
step is not applicable.

Also, what is and what do you mean by extending libpq's published API?

Islam Hegazy

----- Original Message ----- 
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Islam Hegazy" <islheg(at)gmail(dot)com>
Cc: <pgsql-interfaces(at)postgresql(dot)org>
Sent: Saturday, April 21, 2007 8:55 PM
Subject: Re: [INTERFACES] modifying in the libpg files

> "Islam Hegazy" <islheg(at)gmail(dot)com> writes:
>> ../../src/interfaces/libpq/ undefined reference to =
>> `PrintQueryResults'
> is a shared library --- you can't have it calling functions
> that are not in either itself or a shared library it depends on.
> You'd have to move PrintQueryTuples bodily into to make this
> work.  There are various reasons why that's not a great idea, the
> main one being that libpq has no idea where psql is intending to
> send the output.
> IMHO a reasonable solution would involve extending libpq's published API
> to allow returning partial query results.  This seems like it could be
> made to fit into the PQsendQuery/PQgetResult paradigm, but nobody's
> actually done that yet.
> regards, tom lane 

In response to

pgsql-interfaces by date

Next:From: MicazMAKDate: 2007-04-29 16:22:17
Subject: Problem using PQgetvalue()
Previous:From: Tom LaneDate: 2007-04-22 02:55:34
Subject: Re: modifying in the libpg files

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group