Simon Riggs <[EMAIL PROTECTED]> writes:
>> Tom Lane wrote:
>>> The idea that's becoming attractive to me while contemplating the
>>> multiple-maps problem is that we should adopt something similar to
>>> the old Mac OS idea of multiple "forks" in a relation.
> Can we call them "maps" or "metadata maps"? "forks" sounds weird.
I'm not wedded to "forks", that's just the name that was used in the
only previous example I've seen. Classic Mac had a "resource fork"
and a "data fork" within each file.
Don't think I like "maps" though, as (a) that prejudges what the
alternate forks might be used for, and (b) the name fails to be
inclusive of the data fork. Other suggestions anyone?
BTW, thinking about the Mac precedent a little more, I believe
the way they grafted that Classic concept onto BSD was that
applications (which the user thinks of as single objects) are
now directories with multiple files inside them. Probably it'd be
overkill to think of turning each relation into a subdirectory, but
then again maybe not?
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
