From: | Qiqi YU <vonclemay(at)gmail(dot)com> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | rod(at)iol(dot)ie, Pgadmin-Support <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: where are the query output tuples stored |
Date: | 2011-03-13 15:37:41 |
Message-ID: | AANLkTik+yuQK9YTx9fLF4r07LPmmsOiH49vTPtaTT5sO@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Hi Dave,
Thanks for your reply! However, I still have a few doubts:
1: In which stage is the output tuples displayed? Is that within the
OnQueryComplete function?
2: May I know where is this sqlResultTable::GetValue function called?
3: Also what is the difference between ctlSQLResult and sqlResultTable?
Regards
Kevin
2011/3/8 Dave Page <dpage(at)pgadmin(dot)org>:
> On Tue, Mar 8, 2011 at 5:18 PM, Raymond O'Donnell <rod(at)iol(dot)ie> wrote:
>> On 08/03/2011 11:43, Qiqi YU wrote:
>>>
>>> Hi Raymond,
>>>
>>> That could be one possible way.
>>> The thing is I need to extend the current pgAdmin tool, such as adding
>>> a new tuple to the output panel (the output panel would contain many
>>> tuples of resultant data). So which function in pgAdmin does the job
>>> of creating the output table and filling in the data? I have been
>>> using ddd to trace the program, but pgAdmin keeps starting new threads
>>> and lost me.
>>
>> I'm afraid I don't know.... the source code for PgAdmin is at
>> www.pgadmin.org, and the developers are on this list, so maybe they can help
>> you.
>
> The data is stored in a virtual table - the grid accesses it directly
> from the pgSet object we get when we run the query, by using the
> sqlResultTable::GetValue function whenever it wants a value.
>
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2011-03-14 09:16:23 | Re: Git Makefile.am |
Previous Message | Guillaume Lelarge | 2011-03-13 09:54:47 | Re: Bug in pgadmin III v 1.12.2 |