[Babase] repstats Q for Karl
Karl O. Pinc
kop at meme.com
Thu Jun 18 11:28:17 EDT 2009
On 01/15/2009 12:27:42 PM, kfenn wrote:
> Hi Karl,
>
> We have a lady in Repstats (LADHA) who remains in a pregnant state
> for up to 394 days (dins) in 2007 & 2008. She gave birth on 28 May
> 2007 but continues to show up as "P" in the repstats table after this
> date. The birth occurred on day 179 and somewhere I recall that we
> have a rule that includes a 180 day gestation period. Of course this
> sounds nuts because obviously we have stillbirths and aborts before
> 180 days.
>
> Do you have any guesses why she might remain in this state so long?
> Why didn't the birth trigger a change in state in repstats? I
> checked the documentation but I can't find the infosurrounding the
> triggers for change in state.
The basic problem is that the triggers are not updating repstats
or cycstats. Theses must be manually updated by running the
build program whenever any reproductive info is changed.
My guess is that the rebuild_all_repstats program was run
after all the sexual cycle information was entered
but before the birth was entered.
LAD does not have another cycle until 2008-06-06,
so as far as the system is concerned she's still pregnant
until then. Of course after the birth is entered the
next time rebuild_all_repstats is run the repstats
file is fixed -- as we see in the table now.
There's so many things that go into repstats and cycstats
that you almost always need to manually rebuild the
table whenever a change is made. (For example, anything
that changes a statdate.) This is an unhappy situation;
I would much rather have the triggers take care of
repstats and cycstats but we're not there yet.
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