I think that we should also add a column that specifies what hashing
method(s) the hash value is on the row of the part. This would allow 2
things.
1) Re-Calculation of the hash value for a change in hashing methods
could be interrupted and resumed later,
and
2) Message insertion can still occur where as a simple check to see what
hashing methods are use in the table, a new part to be inserted (or not)
can be checked against all hashing methods used (old and new) to ensure
that a duplicate doesn't take place during this migration period.
-Jon
Michael Monnerie wrote:
On Montag, 7. Januar 2008 Paul J Stevens wrote:
Nono, the hash is no-longer the primary key. The primary is now an
auto-increment int.
INT8 (aka BIGINT), I hope.
mfg zmi
------------------------------------------------------------------------
_______________________________________________
DBmail mailing list
DBmail@dbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
DBmail mailing list
DBmail@dbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail
