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

Re: where are the query output tuples stored

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Qiqi YU <vonclemay(at)gmail(dot)com>
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-15 10:44:09
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgadmin-support
On Tue, Mar 15, 2011 at 10:01 AM, Qiqi YU <vonclemay(at)gmail(dot)com> wrote:
> 2011/3/14 Dave Page <dpage(at)pgadmin(dot)org>:
>> On Mon, Mar 14, 2011 at 2:39 PM, Qiqi YU <vonclemay(at)gmail(dot)com> wrote:
>>> Hi Dave,
>>> Thanks for your fast reply. As I went through the code of function
>>> ctlSQLResult::DisplayData(bool single), there seems to be no calling
>>> of wxGrid Control to display data?  My understanding is that the
>>> displayData function would set up the frame of the outputs (i.e. all
>>> the column attributes name and row number). But where is the output
>>> data being inserted into the output table?
>> It's not - you've got it backwards. The grid control calls
>> sqlResultTable::GetValue() whenever it wants to render a cell. That
>> function returns the text to display.
>    For this part, I still can't get it. There are two parts of the
> codes,  executeQuery and onQueryComplete. The displayData function is
> called inside onQueryComplete, so is that pgadmin would  call grid
> control to insert data after it has called the function displayData?

You're still thinking about it backwards. pgAdmin doesn't push the
data into the grid anywhere - you won't see code like
grid->SetCellValue(row, col, value);

In ctlSQLResult::DisplayData(), the important part of the code is this:

         * Resize and repopulate by informing it to delete all the rows and
         * columns, then append the correct number of them. Probably is a
         * better way to do this.
        wxGridTableMessage *msg;
        sqlResultTable *table = (sqlResultTable *)GetTable();
        msg = new wxGridTableMessage(table,
        delete msg;
        msg = new wxGridTableMessage(table,
        delete msg;
        msg = new wxGridTableMessage(table,
        delete msg;
        msg = new wxGridTableMessage(table,
wxGRIDTABLE_NOTIFY_COLS_APPENDED, thread->DataSet()->NumCols());
        delete msg;

What this does is inform the grid that the data in the underlying
table has been changed. First, we tell it that all rows and all
columns have been removed (just so we can start from a clean state).
We then tell it how many rows and columns are currently in the table
(really, the PGresult structure from libpq, encapsulated by the
sqlResultTable class). The grid itself (not pgAdmin) then determines
which cells it needs to render, and for each one, it calls
sqlResultTable::GetValue(). It does this efficiently - it'll work out
which cells it needs to render by looking at whether or not they will
be visible. It then renders a few extra in each direction to ensure
that scrolling doesn't cause any strange effects. From then on, it'll
only render cells when they are about to be scrolled into view.

Dave Page
Twitter: @pgsnake

EnterpriseDB UK:
The Enterprise PostgreSQL Company

In response to

pgadmin-support by date

Next:From: TimonDate: 2011-03-15 10:47:55
Subject: Fwd: [pgadmin-support] Copy & paste - git
Previous:From: Qiqi YUDate: 2011-03-15 10:01:09
Subject: Re: where are the query output tuples stored

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