James,
I think part of your problem is that you’re thinking in terms of the
tables and indexes and so forth that are necessary for a traditional
relational DB. Panorama, both the old versions and the new one, doesn’t
work that way. Since the whole DB is loaded in memory, there is no
necessity for tables and indexes. You just look up what you want and
it’s quick as can be because the whole thing is in RAM. If I understand
what’s going on in this conversation, you’re looking for something that
Panorama doesn’t need in order to do the things you want to do. So
you’ll have to rearrange your mind a bit. I remember going through a
similar process back in the old days when I started using Pan—I had been
using something called Interlace, which became something else and then
was orphaned. Anyhow, I’d suggest going back and thinking about what you
want to do, not how other relational dbs structure it. Hope that helps
further the discusssion.
Have fun,
Bill Conable
James Déraps wrote: