[Babase] Dumptext and dump_as_text for Karl
Leah Gerber
lgerber at duke.edu
Fri Mar 10 16:30:49 EST 2006
Karl,
I have made more changes to the database since I placed a version on
papio. Would you like me to run the dump.txt program and then copy the
data to you again?
Leah
Karl O. Pinc wrote:
> Ok, now that I've made these changes, and now that Leah
> has delivered a new copy of the database we need to
> copy dumptext.prg to foxpro (in HACKS), compile it,
> and run it again. (And copy the results to papio.)
>
> The new copy of dumptext.prg is on the papio webserver.
>
> On 02/15/2006 02:11:13 PM, Catherine Markham wrote:
>> For some reason, I had thought you wanted us to compare dumptext
>> against dump_as_text. When I got into it, though, I realized that of
>> course the two shouldn't match given the changes to database
>> design/structure that go along with the conversion. Right? So I
>> compared dumptext to what's in FoxPro Babase now (I opened up each
>> table in Babase and checked column names). I think when I had
>> originally given you the list of queries when I was first hired, I
>> had compiled everything using the Babase diagram (can't say for sure,
>> though). In any event, I compared dump_as_text to the column
>> names/descriptions in the online documentation. A common mismatch
>> that I noticed was the omission of the unique table id - maybe
>> there's a reason for that, but I listed each one I noticed anyway.
>
>>
>>
>> Possibly missing from dumptext:
>>
>> 1. In RNKTYPES, did you mean to exclude the column for Query?
>
> Missed that. Fixed.
>
>> 2. In GROUPS, did you mean to exclude the column for Lettercode?
>
> Likewise. Fixed.
>
>> 3. In JPSAMPS and FPSAMPS, what about Datetime?
>
> There is no datetime in the new system. Where there's discrepencies
> between Time and Datetime in foxpro this may show up as a difference
> between the old and new databases when we compare, but I figure that's
> ok.
>
>> Possibly missing from dump_as_text:
>>
>> 1. In GROUPS, you list columns for start, finish, and status but I
>> did not see these listed/described in the documentation. Also, do we
>> really want 2 columns called status in the database?
>
> The documentation on GROUPS is not done.
>
> We have lots of Date columns and it does not cause a problem, but
> now's the time if we want to change the column name.
>
>>
>> 2. In CYCLES, what about Series?
>
> Does not exist in foxpro, so there's no comparing.
>>
>> 3. In SEXSKINS, what about Sxid?
>
> ditto
>>
>> 4. In BIOGRAPH, what about Bioid?
>
> ditto
>>
>> 5. In SAMPLES, I saw your note to leave off the Stype but does that
>> also mean Stime and Programid should have been excluded?
>
> ditto
>>
>> 6. In INTERACT, does it matter that the documentation refers to the
>> table as INTERACT_DATA?
>
> No, there is an INTERACT view that should (almost) always be used.
>
> Also, is Sid captured in the query?
>
> Yes, it is.
>
>>
>> 7. In PARTS, what about Partid?
>
> Does not exist in old db so cannot be compared.
>
>>
>> 8. In POINTS as both JPSAMPS and FPSAMPS, what about Min?
>
> ditto
>
> Also, as
>> with INTERACT, does it matter that the documentation refers to the
>> table as POINTS_DATA?
>
> There's a POINTS view.
>
>>
>> 9. In NEIGHBORS as both JPNEIGHBORS and FPNEIGHBORS, what about Nghid?
>
> Does not exist in old db so cannot be compared.
>
>>
>> 10. In ADLIBS, what about Almid?
>
> ditto
>>
>>
>> Questions/Other inconsistencies:
>>
>> 1. In terms of listing all the columns in a particular table,
>> BIOGRAPH in dumptext is missing a few but I figure this is just
>> because you took those missing columns (like matured, dispersed,
>> etc.) and queried them separately.
>
> Right. I hope so anyway.
>>
>> 2. I noticed that when you click on "GROUPS" in the documentation
>> (both in the first, more general table of contents and also under the
>> Chapter 3 heading and specific table of contents there), it seems
>> like the user is redirected to a different discussion of groups (user
>> group and data permission type stuff as opposed to the GROUPS
>> table). The subsections of the GROUPS link make sense to me. Is
>> this a mistake in where the anchor was placed?
>
> I'm not seeing this. Does this happen in firefox or just IE?
> (Or mabe I'm not clicking where you are...? Or maybe I've
> fixed it by accident....)
>
> 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
More information about the Babase
mailing list