[Babase] Partial query results

Karl O. Pinc babase@www.eco.princeton.edu
Wed, 28 Sep 2005 21:03:09 +0000


On 09/28/2005 01:39:49 PM, Catherine Markham wrote:
\
   In the checking of old and new MEMBERS
> tables that goes along with all this, I've noticed a funny quirk a  
> couple times.  When I run a query in the new system, I have had the  
> table stop "processing" without completing all the rows.  This is  
> very rare - I've only noticed it happening maybe 4 or 5 times.  When  
> it does happen, it is pretty obvious because usually I'm checking out  
> the death dates (which aren't loaded because of the cutoff) and there  
> is no total of table rows or time executed listed at the bottom of  
> the webpage.  Just the same, it seems like a potentially dangerous  
> quirk - if the table was thought to be completed and exported, it  
> would be short a lot of data. I played just a little to see I was  
> doing something funky to cause this - can't figure anything out,  
> though.  And the table "load" line does indicate that the page is  
> "done" - in other words, the computer doesn't seem to be momentarily  
> thinking before completely the additional rows.
> 
> Not sure if I explained that well, or if it really is an issue to  
> worry about.  Just thought I'd mention it.

We're using a really old version of the phppgadmin, I think the
thing to do is upgrade and see if it's still happening.
I can also look at the logs and see if anything jumps out.
Also, there could be some sort of limit set somewhere that
we're exceeding that I need to fiddle with.

If we're really concerned then you could read over the
phppgadmin release notes on their website and see if they
say they've fixed a bug like this.  After that we'd ask around
on their mailing list.  When all else fails I fix whatever's
broken and send in the fix.

Karl <kop@meme.com>
Free Software:  "You don't pay back, you pay forward."
                  -- Robert A. Heinlein