[Babase] Dump problem?
Lacey Maryott
lacey.maryott at duke.edu
Wed May 30 12:31:32 EDT 2007
Hey Karl,
According to the changelog, the invalid posture in this sample (R
*S* O S which should be R *2* O S) caused this particular line to be
deleted as per a rule made before about these types of conversion
errors. It looks as thought this was the final conversion error fixed
on the date it was fixed, and it was a day Leah and I were working
together, which means it probably happened around 10-11 pm. So, thinking
we may have just forgotten to remove deleted rows... I looked back in
the latest DBF's I have here (updated may 23) and they have the row in
fpsamps, marked for deletion as well as the row in fpneighbors which is
not marked for deletion. It's odd that this didn't kick out an error on
its own. Tabby is going to keep the FP database until tomorrow and fix
what she needed to fix, but once I get it back, I can just remove the
deleted row, and delete the other. However, I'm not sure why you are
unable to pull up those rows :-\ If Leah used the version we have on
our system here, it makes sense that those rows would have shown up in
the dump.
I'm fearing this investigation uncovered more problems than it fixed.. :-\
sorry for that
Lacey
Karl O. Pinc wrote:
> Hi,
>
> I've got the following errors in comparetables.out:
>
> fpneighbors.TXT
> --- /var/tmp/foxsource.31134 2007-05-30 07:12:06.000000000 -0400
> +++ /var/tmp/postsource.31134 2007-05-30 07:12:08.000000000 -0400
> @@ -259154,7 +259154,6 @@
> 206506 DAS 1
> 206507 DAS 1
> 206508 DAS 1
> -206509 DAS 1
> 206510 DAS 1
> 206510 DAS A
> 206511 DAS 1
> fpsamps.TXT
> --- /var/tmp/foxsource.31134 2007-05-30 07:12:12.000000000 -0400
> +++ /var/tmp/postsource.31134 2007-05-30 07:12:15.000000000 -0400
> @@ -205694,7 +205694,6 @@
> 206506 37058 R 2 O S 15:34
> 206507 37058 R 2 O S 15:36
> 206508 37058 R 2 O S 15:37
> -* 206509 37058 R S O S 15:37
> 206510 37058 R 2 O S 15:38
> 206511 37058 R 2 O S 15:40
> 206512 37058 R 2 O S 15:41
>
> This is telling me that FPSAMPS with fpid 206509 is
> in foxpro but not postgresql. But when I look
> at the fpsamps.dbf file I don't see a 206509.
> I suspect that the * means that the row was deleted
> but somebody didn't do a "PACK" or whatever it is that
> foxpro requires to actually get rid of a deleted row.
>
> Then there's the row in fpneighbors. When I look for
> it in the fpneighbors.dbf file it's not there. This
> leads me to believe that the dump output does not
> exactly correspond to the dbf files.
>
>
> Karl <kop at meme.com>
> Free Software: "You don't pay back, you pay forward."
> -- Robert A. Heinlein
>
> _______________________________________________
> Babase mailing list
> Babase at www.eco.princeton.edu
> http://www.eco.princeton.edu/mailman/listinfo/babase
>
--
Lacey Maryott
Alberts Lab
Department of Biology
Duke University
ph: 919-660-7306
fax: 919-660-7293
Lacey.Maryott at duke.edu
More information about the Babase
mailing list