[Babase] preg upload creates error in cycstats

Karl O. Pinc kop at meme.com
Mon Jan 28 18:46:27 EST 2008


On 01/28/2008 02:07:57 PM, kfenn wrote:
> Karl O. Pinc wrote:
>> 
>> Crud.  I knew not having cycstats/repstats update automatically was
>> going to mean headaches, but I hadn't thought of this one.
>> 
> So if there/ was/ an automatic update, then my trying to delete the  
> mdate would have automatically updated the cycstats too, right?

Right.

  It's
> the fact that the table is static that my changes won't go through...?

Yes.  CYCSTATS does not have much validation, but it does require that
if it references a row on another table, that the referenced row
exist.


  I had that recollection about the cycstats table but I
> couldn't find the right documentation to make me comfortable enough  
> to start deleting stuff from it.

The thing about CYCSTATS is that it's content is (like MEMBERS)
entirely computed based on the content of other tables.  So
it can always be reconstructed from scratch.

>> 
>> The thing to do is delete the CYCSTATS row that's causing the
>> problem, fix things, and then rebuild CYCSTATS.  That'd be
>> how I'd try approaching it.
>> 
>> If you wanted to be brutal, you could delete _all_ the CYCSTATS rows.
>> Rebuilding will rebuild them anyhow.
>> 
> I'm chicken to do the whole thing, though that makes the most sense.   
> I'm just going to start by deleting the cpids that are giving me the  
> error.
> 
>> CYCSTATS and REPSTATS are the one part of the system that's not
>> "automatic".  Programs must be run to manually update them.
>> 
>> It's hard to find the documentation on the programs in the
>> docs.  The REPSTATS/CYCSTATS docs are a bit easier to find,
>> under section "4. Baboon Data: Analyzed", subsection
>> "The Reproductive State Tables".
> 
>> The programs are all in section "9. Babase PROGRAMS", subsection
>> "Useful Programs and Functions".  You either have to hit the
>> "next" link a lot or look at the entire documentation as one
>> giant page.
>> 
> I did eventually find the Ch4 stuff but thanks for directing me to  
> Ch9 and those "next" buttons.  I was missing a whole section.

Frankly the table of contents for those pages is kind of lame.
I haven't really bothered to think too much about it.  I wanted
to structure the function documentation using the markup for
commands, and this puts each function on it's own page.  This
is not a problem, but the table of content depth means these
pages drop off the table of contents.  I've not really thought
about it since I first documented the first functions, and then
I figured I'd better quit fussing and just get on with
the documentation.

So, to
> rebuild the WHOLE table do I use:
> |int *rebuild_cycstats*
> ||
> but to rebuild for just one individual I use:
> || int *rebuild_cycstats* (| sname|)

Yes.  Exactly.

The "everything as one page" documentation link is good
for searching.  Use your browser's search function to look
through the entire document for particulars.

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



More information about the Babase mailing list