Seems that there are complicated requirements for just a basic internal message model such as in Facebook and LinkedIn.
Has anyone modeled messages; have ideas on how to do it? One 1:M idea is to create only one message-body record, and have recipients use a child table that links to body: BODY-table - only one record shared by all recipients ---------- messageID senderID subjectLine messageBody dateSent senderDeleteBoolean (hides from sender, but all recipients that didn't delete can still view) senderArchiveBoolean threadID RECIPIENT-Table --------------- messageID recipientID dateRead archiveBoolean thanks Alex Glaros -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
