云计算存储网站建设安全,中国开头的网站怎么做,欧美平面设计网站,惠州网站建设 惠州邦数据库提取
在 Android Studio 中点击 Device File Explorer按钮。选择/data/data/com.xxx.xxx/databases/bugle_db右键 Save As 保存到本地。注#xff1a;com.xxx.xxx 为当前自己的工程目录
数据库说明
Messaging创建了数据库bugle_db用于同步mms/sms.db的数据#xff…数据库提取
在 Android Studio 中点击 Device File Explorer按钮。选择/data/data/com.xxx.xxx/databases/bugle_db右键 Save As 保存到本地。注com.xxx.xxx 为当前自己的工程目录
数据库说明
Messaging创建了数据库bugle_db用于同步mms/sms.db的数据短信查询时直接从bugle_db数据库进行查询。
数据库内表和视图
conversation_list_view主界面的视图是把conversations、messages和participants三个表的数据糅合起来的视图方便主界面的各项数据显示。conversation_participants记录conversation和它的联系人participatant的关联。messages记录每一条短彩信的数据包括远程uri和已读状态等。parts记录短彩信的实际内容比如文本或者图片uri跟messages关联能得到完整的短彩信数据。
数据库中数据表有 conversations、messages、parts、participants、conversation_participants等。
视图有 draft_parts_view 、coversation_image_parts_view 、conversation_list_view。
数据表
数据表 conversation_participants
字段数据类型说明conversation_idint会话人属于那一场会话participant_idint会话人id
数据表 conversations
字段数据类型说明_idint主键IDsms_thread_idintSMS/MMS Thread ID from the system providernameString信息名称latest_message_idint最新消息idsnippet_textString最新更新的消息的内容彩信为主题短信为正文会话列表中显示的简要消息subject_textString会话列表中显示的简要消息preview_uriString预览Uripreview_content_typeString预览Uri类型show_draftint是否显示当前草稿draft_snippet_textString最新的草稿简要draft_subject_textString最新的草稿主题draft_preview_uriString草稿预览uridraft_preview_content_typeString草稿预览uri类型archive_statusarchive_status会话是否归档sort_timestampint时间戳用于排序last_read_timestampint最新阅读短信时间戳iconString会话Iconparticipant_contact_idint参与者联系人ID如果此对话只有一个参与者。否则为-1participant_lookup_keyString参与者查找键如果此对话只有一个参与者。否则为空participant_normalized_destinationString参与者的标准化目的地如果此对话只有一个参与者。否则为空。current_self_idString自身的idparticipant_countint参与者人数不包括自己因此1:1的比例为1或更大的比例为1:1notification_enabledint对话是否启用通知notification_sound_uriString通知铃声notification_vibrationint是否启动震动include_email_addrint会话包含Emailsms_service_centerStringIS_ENTERPRISEint是否是企业对话is_topint是否置顶后期添加字段
数据表 messages
字段数据类型说明idint主键conversation_idint会话id关联conversations中idsender_idint发送该消息的会话人idsent_timestampint发送消息时间戳received_timestampint接收消息时间戳message_protocolint信息类型短信息、彩信或彩信通知message_statusint消息状态seenint是否被用户在通知中看见0和1readint是否被用户已阅读0和1sms_message_uriString来自平台提供程序的消息IDsms_priorityint信息的优先级sms_message_sizeint彩信大小mms_subjectString彩信主题mms_transaction_idStringMMS通知的事务idmms_content_locationString彩信通知的内容位置mms_expiryint过期时间raw_statusint详细的状态比如那条短信是发送成功还是失败self_idint代表处理此消息的sim卡的参与者retry_start_timestampint开始重试的时间。用于计算重试窗口当重试发送/下载邮件。
数据表 parts
字段数据类型说明_idint主键自增message_idint附件属于那条消息conversation_idint附件属于那次会话textString附件文字uriString附件内容uricontent_typeString附件内容类型widthint此附件的缓存宽度用于加载时的布局heightint此附件的缓存高度用于加载时的布局timestampint同message表中时间戳
数据表 participants
字段数据类型说明_idint主键sub_idint参与者关联的sim卡的订阅id。在L中引入。对于早期版本将始终使用默认的-1。对于多sim卡设备或sim卡已更改的情况单个设备可能有几个不同的sub_id值sim_slot_idint此自参与者的活动SIM插入设备中的插槽。如果自参与者与任何活动SIM不对应这将是链接android.telephony.SubscriptionManager.对于所有非自参与者该列将被忽略normalized_destinationString如果可能电话号码将以标准E164格式存储。这是一个独特的对于给定参与者我们不能用同一个电话号码处理多个参与者因为我们不知道消息来自哪一个。这也可以是电子邮件地址在这种情况下它与显示的地址相同send_destinationString发送短信的号码display_destinationString添加行时根据设备的区域设置对电话号码进行用户友好的格式设置full_nameString全名first_nameString姓profile_photo_uriString头像contact_idint联系人idlookup_keyString包含有关如何在联系人查找中查找联系人信息的提示的字符串blockedint是否该用户被拦截subscription_colorint订阅的颜色subscription_nameString订阅的名字contact_destinationString存储在此参与者的联系人中的确切目的地
视图
conversation_list_view 查询对话列表
SELECT conversations._id AS _id,conversations.name AS name,conversations.current_self_id AS current_self_id,conversations.archive_status AS archive_status,messages.read AS read,conversations.icon AS icon,conversations.participant_contact_id AS participant_contact_id,conversations.participant_lookup_key AS participant_lookup_key,conversations.participant_normalized_destination AS participant_normalized_destination,conversations.sort_timestamp AS sort_timestamp,conversations.show_draft AS show_draft,conversations.draft_snippet_text AS draft_snippet_text,conversations.draft_preview_uri AS draft_preview_uri,conversations.draft_subject_text AS draft_subject_text,conversations.draft_preview_content_type AS draft_preview_content_type,conversations.preview_uri AS preview_uri,conversations.preview_content_type AS preview_content_type,conversations.participant_count AS participant_count,conversations.notification_enabled AS notification_enabled,conversations.notification_sound_uri AS notification_sound_uri,conversations.notification_vibration AS notification_vibration,conversations.include_email_addr AS include_email_addr,messages.message_status AS message_status,messages.raw_status AS raw_status,messages._id AS message_id,participants.first_name AS snippet_sender_first_name,participants.display_destination AS snippet_sender_display_destination,conversations.IS_ENTERPRISE AS IS_ENTERPRISE,conversations.is_top AS is_top,conversations.snippet_text AS snippet_text,conversations.subject_text AS subject_textFROM conversationsLEFT JOINmessages ON (conversations.latest_message_id messages._id) LEFT JOINparticipants ON (messages.sender_id participants._id) ORDER BY conversations.sort_timestamp DESC;coversation_image_parts_view 查询图片列表
SELECT messages.conversation_id AS conversation_id,parts.uri AS uri,participants.full_name AS _display_name,parts.uri AS contentUri,NULL AS thumbnailUri,parts.content_type AS contentType,participants.display_destination AS display_destination,messages.received_timestamp AS received_timestamp,messages.message_status AS message_statusFROM messagesLEFT JOINparts ON (messages._id parts.message_id) LEFT JOINparticipants ON (messages.sender_id participants._id) WHERE parts.content_type LIKE image/%ORDER BY messages.received_timestamp ASC,parts._id ASC;draft_parts_view 查询草稿附件
SELECT parts._id AS _id,parts.message_id AS message_id,parts.text AS text,parts.uri AS uri,parts.content_type AS content_type,parts.width AS width,parts.height AS height,messages.conversation_id AS conversation_idFROM messagesLEFT JOINparts ON (messages._id parts.message_id) WHERE messages.message_status 3;参考 安卓短信Messaging数据库表格整理与字段分析
