Handle more SMS/MMS features
This issue is for handling more details in SMS and MMS chats.
I created the possible db schema documentation as a comment so as to use when we want better sms/mms support,
- send time and delivered time is different for sms/mms (and we can have both info)
- we want to store smsc if we have a setting for replying with the same smsc
- and we will have to store the sms reference number so that we can track sms delivery state even after chatty is restart
The following sql schema may be helpful as we implement them:
"CREATE TABLE IF NOT EXISTS sms (" "id INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT, " "text TEXT, " "smsc TEXT, " /* mm_sms_get_message_reference(), for outgoing only? */ "sms_reference INTEGER, " /* For incoming sms this is the advertised time in the received sms * For outgoing sms this is the sms delivery time */ /* XXX: the informed time can contain timezone information. Should we use string? */ "time_sent INTEGER," /* Set only for outgoing sms */ "validity INTEGER;" /* body_id can refer sms or files (or just use body?) */ "ALTER TABLE messages ADD COLUMN body_id INTEGER;"
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information