>>>>> "PR" == Peter Riocreux <[EMAIL PROTECTED]> writes:
PR> If we are talking wholesale reforms here, we ought to move away
PR> from the name being the primary index key first I would have
PR> thought, to allow multiple identical names in the DB.
This is or will be done shortly. It still uses the persons name
as a major hash key but everything is now deals with the fact that
multiple records hash to the same value.
So for example if I do (bbdb-display "Eastman Kodak")\ I will get
everyone in my BBDB that has "Eastman Kodak" as their Company field
(BBDB has always hashed on company name it's just that now it tracks
more than one person per company).
Now that I think about it a 'bbdb-hash-hook' that get's called
with each record and returns a list of strings to hash the record
under, might be nice (although handling updates might be killer).
PR> This could also allow BBDB to prompt for new record creation when
PR> a new address is seen or an existing name. This reminds me, when
PR> it mentions name mismatches, it could offer some way to remedy it
PR> (by adding an AKA perhaps).
I must be be misunderstanding something here. My BBDB already
does this (and has done it since before my 'duplicate record' patch).
This behavior is controlled by a number of variables, the two I use
are:
bbdb-notice-hook
bbdb-ignore-most-messages-alist
--
Thomas DeWeese
[EMAIL PROTECTED]
"The only difference between theory and practice is
that in theory there isn't any." -- unknown
_______________________________________________
bbdb-info mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/bbdb-info
