Hi Gordon,
You <GM> wrote on Thursday (2/26/2004 at 12:18) thus about [Metakit] data structure
question:
>> 1) create a separate temporary view for each type and manually copy
>> the flattened view into it, creating and setting 'type'
>> appropriately. Then union off of these PyView objects.
>> 2) or modify my system to always write the subview type into the
>> subview. This means extra programming and run-time overhead, and
>> extra strings in tens of thousands of records.
>> 3) or some other creative idea you suggest.
GM> I don't really grasp what you're trying to do, but 2 things come
GM> to mind:
GM> 1) view.rename("value", "newvalue") might help
GM> 2) tmp = vw[:] will turn a ROViewer into a (in memory) View, so you
GM> could add a column.
GM> I wouldn't worry too much about processing time - what you're
GM> doing is already pretty intensive.
GM> -- Gordon
Thanks for the reply. Sorry my explanation wasn't clear. Your #2
looked promising, but the resulting 'tmp' is still PyROViewer on my
system (MK 2.4.9.2). So it looks like I am going to have to read the
properties from my ROViewer, write a routine to add those properties
onto a new view on a temporary storage, then copy my rows over each
time I flatten a sub-view.
As to #1, I really don't want to rename the rows. I want all the
values in columns "key" and "val" from three sub-views to be in "key"
and "val" in the new flattened view. I just want to know which
sub-view they came from!
--
Jerry (Mailed safely with The Bat! 2.02.3 CE)
___________________________
Let the people know the truth and the country is safe. --Abraham Lincoln
_____________________________________________
Metakit mailing list - [EMAIL PROTECTED]
http://www.equi4.com/mailman/listinfo/metakit
