The Tiki SQL Database Table tiki_comments has hash data (I suspect is an MD5 hash). That hash data is used in establishing a unique message_id for each comment message.
I've been unable to determine if that comment hash data is used anywhere else, and that is my first question: Is the hash data that is stored in the tiki_comments table used for anything other than in the comments_id table?
If it is used somewhere else, then: Does that 'hash data' then need to be hex compliant? (The message_id is alpha-numeric, so it's not limited to just the hex '0-f' range of the hash output. ).
BONUS (curiosity) QUESTION: What record data elements are being concatenated and hashed to generate that 'unique' hash code?
'Why do I ask?', you ask? I'm going to be stuffing forum messages from another forum system (non-tiki) into the tiki forum, and I want to be sure that whatever data in the hash record (if any) that I associate with the message for importing is sufficiently unique and compatible if it is indeed being referred to elsewhere in the tiki CMS system.
If that data is not used anywhere else (and is merely a repository for the hashing output process to subsequently be used to generate the message_id (only), then I need not worry about it's hex-compliance, and may not even need to populate that column.