|
|
|
@ -0,0 +1,760 @@
|
|
|
|
|
/*
|
|
|
|
|
* Copyright (c) 2010-2011, The MiCode Open Source Community (www.micode.net)
|
|
|
|
|
*
|
|
|
|
|
* Licensed under the Apache License, Version 2.0 (the "License");
|
|
|
|
|
* you may not use this file except in compliance with the License.
|
|
|
|
|
* You may obtain a copy of the License at
|
|
|
|
|
*
|
|
|
|
|
* http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
|
*
|
|
|
|
|
* Unless required by applicable law or agreed to in writing, software
|
|
|
|
|
* distributed under the License is distributed on an "AS IS" BASIS,
|
|
|
|
|
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
|
|
|
* See the License for the specific language governing permissions and
|
|
|
|
|
* limitations under the License.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
package net.micode.notes.data;
|
|
|
|
|
|
|
|
|
|
import android.content.ContentValues;
|
|
|
|
|
import android.content.Context;
|
|
|
|
|
import android.database.sqlite.SQLiteDatabase;
|
|
|
|
|
import android.database.sqlite.SQLiteOpenHelper;
|
|
|
|
|
import android.util.Log;
|
|
|
|
|
|
|
|
|
|
import net.micode.notes.data.Notes.DataColumns;
|
|
|
|
|
import net.micode.notes.data.Notes.DataConstants;
|
|
|
|
|
import net.micode.notes.data.Notes.NoteColumns;
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* 数据库辅助类,管理SQLite数据库的创建、升级和降级
|
|
|
|
|
* 继承自Android SQLiteOpenHelper抽象类,实现数据库生命周期管理
|
|
|
|
|
*/
|
|
|
|
|
public class NotesDatabaseHelper extends SQLiteOpenHelper {
|
|
|
|
|
|
|
|
|
|
// ========================
|
|
|
|
|
// 数据库元数据(名称、版本)
|
|
|
|
|
// ========================
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* 数据库文件名称(存储于应用私有目录,路径为:data/data/包名/databases/note.db)
|
|
|
|
|
*/
|
|
|
|
|
private static final String DB_NAME = "note.db";
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* 数据库版本号(用于版本升级检测,必须按自然数递增)
|
|
|
|
|
*/
|
|
|
|
|
private static final int DB_VERSION = 4;
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
// ========================
|
|
|
|
|
// 数据库表名接口(常量集中管理)
|
|
|
|
|
// ========================
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* 数据库表名常量接口
|
|
|
|
|
* 集中管理表名,避免魔法字符串散落各处
|
|
|
|
|
*/
|
|
|
|
|
public interface TABLE {
|
|
|
|
|
/**
|
|
|
|
|
* 笔记/文件夹主表(存储基础信息,如标题、类型、时间戳等)
|
|
|
|
|
*/
|
|
|
|
|
public static final String NOTE = "note";
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* 笔记附件数据表(存储多媒体内容、扩展字段等)
|
|
|
|
|
*/
|
|
|
|
|
public static final String DATA = "data";
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
private static final String TAG = "NotesDatabaseHelper"; // 日志标签,用于调试输出
|
|
|
|
|
|
|
|
|
|
private static NotesDatabaseHelper mInstance; // 单例实例,确保全局唯一数据库连接
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* 创建笔记/文件夹主表的SQL语句
|
|
|
|
|
* 表结构说明:
|
|
|
|
|
* - 存储笔记和文件夹的基础信息,通过{@link NoteColumns#TYPE}字段区分类型
|
|
|
|
|
* - 使用自增主键{@link NoteColumns#ID},符合SQLite规范
|
|
|
|
|
* - 字段默认值遵循业务逻辑(如未指定父文件夹时默认归属根目录)
|
|
|
|
|
*/
|
|
|
|
|
private static final String CREATE_NOTE_TABLE_SQL =
|
|
|
|
|
"CREATE TABLE " + TABLE.NOTE + "(" +
|
|
|
|
|
// 主键:唯一标识记录(INTEGER PRIMARY KEY 自动自增)
|
|
|
|
|
NoteColumns.ID + " INTEGER PRIMARY KEY," +
|
|
|
|
|
|
|
|
|
|
// 父文件夹ID:默认值0表示根文件夹({@link Notes#ID_ROOT_FOLDER})
|
|
|
|
|
NoteColumns.PARENT_ID + " INTEGER NOT NULL DEFAULT 0," +
|
|
|
|
|
|
|
|
|
|
// 提醒时间戳:默认0表示无提醒(毫秒级时间戳)
|
|
|
|
|
NoteColumns.ALERTED_DATE + " INTEGER NOT NULL DEFAULT 0," +
|
|
|
|
|
|
|
|
|
|
// 背景颜色ID:默认0表示默认颜色(对应R.color资源ID)
|
|
|
|
|
NoteColumns.BG_COLOR_ID + " INTEGER NOT NULL DEFAULT 0," +
|
|
|
|
|
|
|
|
|
|
// 创建时间:默认值为当前时间戳(strftime('%s','now')*1000 转换为毫秒)
|
|
|
|
|
NoteColumns.CREATED_DATE + " INTEGER NOT NULL DEFAULT (strftime('%s','now') * 1000)," +
|
|
|
|
|
|
|
|
|
|
// 是否有附件:默认0表示纯文本笔记(1=有附件,0=无)
|
|
|
|
|
NoteColumns.HAS_ATTACHMENT + " INTEGER NOT NULL DEFAULT 0," +
|
|
|
|
|
|
|
|
|
|
// 最后修改时间:默认值为当前时间戳(自动更新)
|
|
|
|
|
NoteColumns.MODIFIED_DATE + " INTEGER NOT NULL DEFAULT (strftime('%s','now') * 1000)," +
|
|
|
|
|
|
|
|
|
|
// 子项数量:文件夹类型有效,默认0表示空文件夹
|
|
|
|
|
NoteColumns.NOTES_COUNT + " INTEGER NOT NULL DEFAULT 0," +
|
|
|
|
|
|
|
|
|
|
// 摘要内容:文件夹名称或笔记正文摘要,默认空字符串
|
|
|
|
|
NoteColumns.SNIPPET + " TEXT NOT NULL DEFAULT '','" +
|
|
|
|
|
|
|
|
|
|
// 数据类型:0=笔记,1=文件夹,2=系统项(默认0为普通笔记)
|
|
|
|
|
NoteColumns.TYPE + " INTEGER NOT NULL DEFAULT 0," +
|
|
|
|
|
|
|
|
|
|
// 桌面小部件ID:默认0表示未关联小部件(对应AppWidgetManager的ID)
|
|
|
|
|
NoteColumns.WIDGET_ID + " INTEGER NOT NULL DEFAULT 0," +
|
|
|
|
|
|
|
|
|
|
// 小部件类型:默认-1表示无效类型(对应{@link Notes#TYPE_WIDGET_INVALIDE})
|
|
|
|
|
NoteColumns.WIDGET_TYPE + " INTEGER NOT NULL DEFAULT -1," +
|
|
|
|
|
|
|
|
|
|
// 同步ID:默认0表示未同步(用于与服务器数据关联)
|
|
|
|
|
NoteColumns.SYNC_ID + " INTEGER NOT NULL DEFAULT 0," +
|
|
|
|
|
|
|
|
|
|
// 本地修改标记:默认0表示已同步(1=本地修改未同步)
|
|
|
|
|
NoteColumns.LOCAL_MODIFIED + " INTEGER NOT NULL DEFAULT 0," +
|
|
|
|
|
|
|
|
|
|
// 原始父文件夹ID:默认0表示未移动过(用于临时文件夹逻辑)
|
|
|
|
|
NoteColumns.ORIGIN_PARENT_ID + " INTEGER NOT NULL DEFAULT 0," +
|
|
|
|
|
|
|
|
|
|
// Google Tasks ID:默认空字符串(用于同步到Google Tasks)
|
|
|
|
|
NoteColumns.GTASK_ID + " TEXT NOT NULL DEFAULT '','" +
|
|
|
|
|
|
|
|
|
|
// 数据版本号:默认0(用于冲突检测和数据升级)
|
|
|
|
|
NoteColumns.VERSION + " INTEGER NOT NULL DEFAULT 0" +
|
|
|
|
|
")";
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* 创建笔记附件数据表的SQL语句
|
|
|
|
|
* 表结构说明:
|
|
|
|
|
* - 存储与笔记关联的扩展数据(如多媒体内容、富文本等)
|
|
|
|
|
* - 通过{@link DataColumns#NOTE_ID}外键关联主表(note表)
|
|
|
|
|
* - 使用通用字段{@link DataColumns#DATA1}~{@link DataColumns#DATA5}支持灵活数据类型扩展
|
|
|
|
|
*/
|
|
|
|
|
private static final String CREATE_DATA_TABLE_SQL =
|
|
|
|
|
"CREATE TABLE " + TABLE.DATA + "(" +
|
|
|
|
|
// 主键:唯一标识记录(自增ID)
|
|
|
|
|
DataColumns.ID + " INTEGER PRIMARY KEY," +
|
|
|
|
|
|
|
|
|
|
// MIME类型:必须非空(如"text/plain"、"image/jpeg")
|
|
|
|
|
DataColumns.MIME_TYPE + " TEXT NOT NULL," +
|
|
|
|
|
|
|
|
|
|
// 关联的笔记ID:默认0(需通过代码确保外键有效性,SQLite需启用外键约束)
|
|
|
|
|
DataColumns.NOTE_ID + " INTEGER NOT NULL DEFAULT 0," +
|
|
|
|
|
|
|
|
|
|
// 创建时间:默认当前时间戳(毫秒)
|
|
|
|
|
NoteColumns.CREATED_DATE + " INTEGER NOT NULL DEFAULT (strftime('%s','now') * 1000)," +
|
|
|
|
|
|
|
|
|
|
// 最后修改时间:默认当前时间戳(毫秒)
|
|
|
|
|
NoteColumns.MODIFIED_DATE + " INTEGER NOT NULL DEFAULT (strftime('%s','now') * 1000)," +
|
|
|
|
|
|
|
|
|
|
// 数据内容:文本内容或文件路径(默认空字符串)
|
|
|
|
|
DataColumns.CONTENT + " TEXT NOT NULL DEFAULT '','" +
|
|
|
|
|
|
|
|
|
|
// 通用整数字段:含义由MIME类型决定(如文本笔记的模式字段)
|
|
|
|
|
DataColumns.DATA1 + " INTEGER," +
|
|
|
|
|
|
|
|
|
|
// 通用整数字段:备用扩展字段
|
|
|
|
|
DataColumns.DATA2 + " INTEGER," +
|
|
|
|
|
|
|
|
|
|
// 通用字符串字段:如电话号码、标签等
|
|
|
|
|
DataColumns.DATA3 + " TEXT NOT NULL DEFAULT '','" +
|
|
|
|
|
|
|
|
|
|
// 通用字符串字段:备用扩展字段
|
|
|
|
|
DataColumns.DATA4 + " TEXT NOT NULL DEFAULT '','" +
|
|
|
|
|
|
|
|
|
|
// 通用字符串字段:备用扩展字段
|
|
|
|
|
DataColumns.DATA5 + " TEXT NOT NULL DEFAULT ''" +
|
|
|
|
|
")";
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* 创建DATA表的note_id索引的SQL语句
|
|
|
|
|
* 索引作用:
|
|
|
|
|
* - 加速通过{@link DataColumns#NOTE_ID}查询关联数据的速度
|
|
|
|
|
* - 减少表连接操作的时间复杂度(特别是在查询笔记及其附件时)
|
|
|
|
|
*/
|
|
|
|
|
private static final String CREATE_DATA_NOTE_ID_INDEX_SQL =
|
|
|
|
|
"CREATE INDEX IF NOT EXISTS note_id_index ON " +
|
|
|
|
|
TABLE.DATA + "(" + DataColumns.NOTE_ID + ");";
|
|
|
|
|
/**
|
|
|
|
|
* Increase folder's note count when move note to the folder
|
|
|
|
|
*/
|
|
|
|
|
/**
|
|
|
|
|
* 当笔记的父文件夹ID(PARENT_ID)更新时,增加目标文件夹的笔记计数
|
|
|
|
|
* 触发条件:
|
|
|
|
|
* - 对note表执行UPDATE操作,且更新字段包含{@link NoteColumns#PARENT_ID}
|
|
|
|
|
* 逻辑说明:
|
|
|
|
|
* - `new.PARENT_ID`表示更新后的父文件夹ID
|
|
|
|
|
* - 通过更新目标文件夹(ID=new.PARENT_ID)的NOTES_COUNT字段实现计数增加
|
|
|
|
|
*/
|
|
|
|
|
private static final String NOTE_INCREASE_FOLDER_COUNT_ON_UPDATE_TRIGGER =
|
|
|
|
|
"CREATE TRIGGER increase_folder_count_on_update " +
|
|
|
|
|
"AFTER UPDATE OF " + NoteColumns.PARENT_ID + " ON " + TABLE.NOTE +
|
|
|
|
|
"BEGIN " +
|
|
|
|
|
" UPDATE " + TABLE.NOTE +
|
|
|
|
|
" SET " + NoteColumns.NOTES_COUNT + " = " + NoteColumns.NOTES_COUNT + " + 1 " +
|
|
|
|
|
" WHERE " + NoteColumns.ID + " = new." + NoteColumns.PARENT_ID + ";" +
|
|
|
|
|
"END";
|
|
|
|
|
/**
|
|
|
|
|
* Decrease folder's note count when move note from folder
|
|
|
|
|
*/
|
|
|
|
|
/**
|
|
|
|
|
* 当笔记的父文件夹ID(PARENT_ID)更新时,减少原文件夹的笔记计数
|
|
|
|
|
* 触发条件:
|
|
|
|
|
* - 对note表执行UPDATE操作,且更新字段包含{@link NoteColumns#PARENT_ID}
|
|
|
|
|
* 逻辑说明:
|
|
|
|
|
* - `old.PARENT_ID`表示更新前的父文件夹ID
|
|
|
|
|
* - 仅当原文件夹的NOTES_COUNT > 0时执行减少操作(避免负数)
|
|
|
|
|
*/
|
|
|
|
|
private static final String NOTE_DECREASE_FOLDER_COUNT_ON_UPDATE_TRIGGER =
|
|
|
|
|
"CREATE TRIGGER decrease_folder_count_on_update " +
|
|
|
|
|
"AFTER UPDATE OF " + NoteColumns.PARENT_ID + " ON " + TABLE.NOTE +
|
|
|
|
|
"BEGIN " +
|
|
|
|
|
" UPDATE " + TABLE.NOTE +
|
|
|
|
|
" SET " + NoteColumns.NOTES_COUNT + " = " + NoteColumns.NOTES_COUNT + " - 1 " +
|
|
|
|
|
" WHERE " + NoteColumns.ID + " = old." + NoteColumns.PARENT_ID + " " +
|
|
|
|
|
" AND " + NoteColumns.NOTES_COUNT + " > 0;" +
|
|
|
|
|
"END";
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Increase folder's note count when insert new note to the folder
|
|
|
|
|
*/
|
|
|
|
|
/**
|
|
|
|
|
* 当新笔记插入到note表时,增加所属文件夹的笔记计数
|
|
|
|
|
* 触发条件:
|
|
|
|
|
* - 对note表执行INSERT操作
|
|
|
|
|
* 逻辑说明:
|
|
|
|
|
* - `new.PARENT_ID`表示新笔记的父文件夹ID(默认0为根文件夹)
|
|
|
|
|
* - 通过更新所属文件夹(ID=new.PARENT_ID)的NOTES_COUNT字段实现计数增加
|
|
|
|
|
*/
|
|
|
|
|
private static final String NOTE_INCREASE_FOLDER_COUNT_ON_INSERT_TRIGGER =
|
|
|
|
|
"CREATE TRIGGER increase_folder_count_on_insert " +
|
|
|
|
|
"AFTER INSERT ON " + TABLE.NOTE +
|
|
|
|
|
"BEGIN " +
|
|
|
|
|
" UPDATE " + TABLE.NOTE +
|
|
|
|
|
" SET " + NoteColumns.NOTES_COUNT + " = " + NoteColumns.NOTES_COUNT + " + 1 " +
|
|
|
|
|
" WHERE " + NoteColumns.ID + " = new." + NoteColumns.PARENT_ID + ";" +
|
|
|
|
|
"END";
|
|
|
|
|
/**
|
|
|
|
|
* Decrease folder's note count when delete note from the folder
|
|
|
|
|
*/
|
|
|
|
|
/**
|
|
|
|
|
* 当笔记被删除时,减少其父文件夹的笔记计数
|
|
|
|
|
* 触发条件:
|
|
|
|
|
* - 对note表执行DELETE操作
|
|
|
|
|
* 逻辑说明:
|
|
|
|
|
* - `old.PARENT_ID`表示被删除笔记的原父文件夹ID
|
|
|
|
|
* - 仅当父文件夹的NOTES_COUNT > 0时执行减少操作,避免计数为负数
|
|
|
|
|
* - 适用于删除笔记或文件夹时的计数维护(文件夹删除需级联处理其子项)
|
|
|
|
|
*/
|
|
|
|
|
private static final String NOTE_DECREASE_FOLDER_COUNT_ON_DELETE_TRIGGER =
|
|
|
|
|
"CREATE TRIGGER decrease_folder_count_on_delete " +
|
|
|
|
|
"AFTER DELETE ON " + TABLE.NOTE +
|
|
|
|
|
"BEGIN " +
|
|
|
|
|
" UPDATE " + TABLE.NOTE +
|
|
|
|
|
" SET " + NoteColumns.NOTES_COUNT + " = " + NoteColumns.NOTES_COUNT + " - 1 " +
|
|
|
|
|
" WHERE " + NoteColumns.ID + " = old." + NoteColumns.PARENT_ID + " " +
|
|
|
|
|
" AND " + NoteColumns.NOTES_COUNT + " > 0;" +
|
|
|
|
|
"END";
|
|
|
|
|
/**
|
|
|
|
|
* Update note's content when insert data with type {@link DataConstants#NOTE}
|
|
|
|
|
*/
|
|
|
|
|
/**
|
|
|
|
|
* 当插入数据记录且MIME类型为文本笔记时,更新主表中的笔记内容摘要
|
|
|
|
|
* 触发条件:
|
|
|
|
|
* - 对data表执行INSERT操作
|
|
|
|
|
* - 新增记录的MIME_TYPE等于{@link DataConstants#NOTE}(即"vnd.android.cursor.item/text_note")
|
|
|
|
|
* 逻辑说明:
|
|
|
|
|
* - `new.NOTE_ID`表示新增数据关联的笔记ID
|
|
|
|
|
* - `new.CONTENT`为文本笔记的内容,同步至主表的SNIPPET字段
|
|
|
|
|
* - 实现数据表与主表的内容联动(如文本笔记的正文存储于data表,摘要显示于note表)
|
|
|
|
|
*/
|
|
|
|
|
private static final String DATA_UPDATE_NOTE_CONTENT_ON_INSERT_TRIGGER =
|
|
|
|
|
"CREATE TRIGGER update_note_content_on_insert " +
|
|
|
|
|
"AFTER INSERT ON " + TABLE.DATA +
|
|
|
|
|
"WHEN new." + DataColumns.MIME_TYPE + " = '" + DataConstants.NOTE + "' " +
|
|
|
|
|
"BEGIN " +
|
|
|
|
|
" UPDATE " + TABLE.NOTE +
|
|
|
|
|
" SET " + NoteColumns.SNIPPET + " = new." + DataColumns.CONTENT +
|
|
|
|
|
" WHERE " + NoteColumns.ID + " = new." + DataColumns.NOTE_ID + ";" +
|
|
|
|
|
"END";
|
|
|
|
|
/**
|
|
|
|
|
* Update note's content when data with {@link DataConstants#NOTE} type has changed
|
|
|
|
|
*/
|
|
|
|
|
/**
|
|
|
|
|
* 当更新数据记录且原MIME类型为文本笔记时,更新主表中的笔记内容摘要
|
|
|
|
|
* 触发条件:
|
|
|
|
|
* - 对data表执行UPDATE操作
|
|
|
|
|
* - 更新前的MIME_TYPE等于{@link DataConstants#NOTE}(确保仅文本笔记数据触发)
|
|
|
|
|
* 逻辑说明:
|
|
|
|
|
* - `old.MIME_TYPE`用于判断数据类型是否为文本笔记(避免其他类型数据误触发)
|
|
|
|
|
* - `new.CONTENT`为更新后的内容,同步至主表的SNIPPET字段
|
|
|
|
|
* - 保证数据修改后,主表摘要与附件表内容一致
|
|
|
|
|
*/
|
|
|
|
|
private static final String DATA_UPDATE_NOTE_CONTENT_ON_UPDATE_TRIGGER =
|
|
|
|
|
"CREATE TRIGGER update_note_content_on_update " +
|
|
|
|
|
"AFTER UPDATE ON " + TABLE.DATA +
|
|
|
|
|
"WHEN old." + DataColumns.MIME_TYPE + " = '" + DataConstants.NOTE + "' " +
|
|
|
|
|
"BEGIN " +
|
|
|
|
|
" UPDATE " + TABLE.NOTE +
|
|
|
|
|
" SET " + NoteColumns.SNIPPET + " = new." + DataColumns.CONTENT +
|
|
|
|
|
" WHERE " + NoteColumns.ID + " = new." + DataColumns.NOTE_ID + ";" +
|
|
|
|
|
"END";
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Update note's content when data with {@link DataConstants#NOTE} type has deleted
|
|
|
|
|
*/
|
|
|
|
|
/**
|
|
|
|
|
* 当删除数据记录且原MIME类型为文本笔记时,清空主表中的笔记内容摘要
|
|
|
|
|
* 触发条件:
|
|
|
|
|
* - 对data表执行DELETE操作
|
|
|
|
|
* - 删除前的记录MIME_TYPE等于{@link DataConstants#NOTE}(即文本笔记类型)
|
|
|
|
|
* 逻辑说明:
|
|
|
|
|
* - `old.NOTE_ID`表示被删除数据关联的笔记ID
|
|
|
|
|
* - 将主表中对应笔记的SNIPPET字段设置为空字符串(''),确保数据删除后摘要与内容一致
|
|
|
|
|
* - 适用于文本笔记内容被完全删除的场景(如用户清空笔记正文)
|
|
|
|
|
*/
|
|
|
|
|
private static final String DATA_UPDATE_NOTE_CONTENT_ON_DELETE_TRIGGER =
|
|
|
|
|
"CREATE TRIGGER update_note_content_on_delete " +
|
|
|
|
|
"AFTER DELETE ON " + TABLE.DATA +
|
|
|
|
|
"WHEN old." + DataColumns.MIME_TYPE + " = '" + DataConstants.NOTE + "' " +
|
|
|
|
|
"BEGIN " +
|
|
|
|
|
" UPDATE " + TABLE.NOTE +
|
|
|
|
|
" SET " + NoteColumns.SNIPPET + " = '' " +
|
|
|
|
|
" WHERE " + NoteColumns.ID + " = old." + DataColumns.NOTE_ID + ";" +
|
|
|
|
|
"END";
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Delete datas belong to note which has been deleted
|
|
|
|
|
*/
|
|
|
|
|
/**
|
|
|
|
|
* 当删除数据记录且原MIME类型为文本笔记时,清空主表中的笔记内容摘要
|
|
|
|
|
* 触发条件:
|
|
|
|
|
* - 对data表执行DELETE操作
|
|
|
|
|
* - 删除前的记录MIME_TYPE等于{@link DataConstants#NOTE}(即文本笔记类型)
|
|
|
|
|
* 逻辑说明:
|
|
|
|
|
* - `old.NOTE_ID`表示被删除数据关联的笔记ID
|
|
|
|
|
* - 将主表中对应笔记的SNIPPET字段设置为空字符串(''),确保数据删除后摘要与内容一致
|
|
|
|
|
* - 适用于文本笔记内容被完全删除的场景(如用户清空笔记正文)
|
|
|
|
|
*/
|
|
|
|
|
private static final String DATA_UPDATE_NOTE_CONTENT_ON_DELETE_TRIGGER =
|
|
|
|
|
"CREATE TRIGGER update_note_content_on_delete " +
|
|
|
|
|
"AFTER DELETE ON " + TABLE.DATA +
|
|
|
|
|
"WHEN old." + DataColumns.MIME_TYPE + " = '" + DataConstants.NOTE + "' " +
|
|
|
|
|
"BEGIN " +
|
|
|
|
|
" UPDATE " + TABLE.NOTE +
|
|
|
|
|
" SET " + NoteColumns.SNIPPET + " = '' " +
|
|
|
|
|
" WHERE " + NoteColumns.ID + " = old." + DataColumns.NOTE_ID + ";" +
|
|
|
|
|
"END";
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Delete notes belong to folder which has been deleted
|
|
|
|
|
*/
|
|
|
|
|
/**
|
|
|
|
|
* 当文件夹被删除时,自动删除其包含的所有子笔记
|
|
|
|
|
* 触发条件:
|
|
|
|
|
* - 对note表执行DELETE操作(删除的记录类型为文件夹)
|
|
|
|
|
* 逻辑说明:
|
|
|
|
|
* - `old.ID`表示被删除文件夹的ID
|
|
|
|
|
* - 通过`NoteColumns.PARENT_ID`关联,删除note表中所有父文件夹为该ID的记录
|
|
|
|
|
* - 实现简单的级联删除(仅处理直接子项,不递归删除子文件夹)
|
|
|
|
|
* - 注:需配合业务逻辑处理嵌套文件夹的递归删除
|
|
|
|
|
*/
|
|
|
|
|
private static final String FOLDER_DELETE_NOTES_ON_DELETE_TRIGGER =
|
|
|
|
|
"CREATE TRIGGER folder_delete_notes_on_delete " +
|
|
|
|
|
"AFTER DELETE ON " + TABLE.NOTE +
|
|
|
|
|
"BEGIN " +
|
|
|
|
|
" DELETE FROM " + TABLE.NOTE +
|
|
|
|
|
" WHERE " + NoteColumns.PARENT_ID + " = old." + NoteColumns.ID + ";" +
|
|
|
|
|
"END";
|
|
|
|
|
/**
|
|
|
|
|
* Move notes belong to folder which has been moved to trash folder
|
|
|
|
|
*/
|
|
|
|
|
/**
|
|
|
|
|
* 当文件夹被移动到回收站时,自动将其所有子笔记也移动到回收站
|
|
|
|
|
* 触发条件:
|
|
|
|
|
* - 对note表执行UPDATE操作
|
|
|
|
|
* - 更新后文件夹的PARENT_ID等于回收站文件夹ID(Notes.ID_TRASH_FOLER)
|
|
|
|
|
* 逻辑说明:
|
|
|
|
|
* - 将被移动文件夹的所有直接子项(PARENT_ID=old.ID)的父级也设置为回收站ID
|
|
|
|
|
* - 实现文件夹与子笔记的级联移动,确保数据完整性
|
|
|
|
|
* 注意:
|
|
|
|
|
* - 仅处理直接子项,不递归处理子文件夹的子项(需业务层配合递归移动)
|
|
|
|
|
*/
|
|
|
|
|
private static final String FOLDER_MOVE_NOTES_ON_TRASH_TRIGGER =
|
|
|
|
|
"CREATE TRIGGER folder_move_notes_on_trash " +
|
|
|
|
|
"AFTER UPDATE ON " + TABLE.NOTE +
|
|
|
|
|
"WHEN new." + NoteColumns.PARENT_ID + "=" + Notes.ID_TRASH_FOLER +
|
|
|
|
|
"BEGIN" +
|
|
|
|
|
" UPDATE " + TABLE.NOTE +
|
|
|
|
|
" SET " + NoteColumns.PARENT_ID + "=" + Notes.ID_TRASH_FOLER +
|
|
|
|
|
" WHERE " + NoteColumns.PARENT_ID + "=old." + NoteColumns.ID + ";" +
|
|
|
|
|
"END";
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* 构造方法
|
|
|
|
|
* 初始化数据库辅助类实例
|
|
|
|
|
*
|
|
|
|
|
* @param context 应用上下文
|
|
|
|
|
*/
|
|
|
|
|
public NotesDatabaseHelper(Context context) {
|
|
|
|
|
// 调用父类构造器,传递数据库名和版本号
|
|
|
|
|
super(context, DB_NAME, null, DB_VERSION);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* 创建笔记表及相关触发器,并初始化系统文件夹
|
|
|
|
|
* 注意:此方法仅在数据库升级或重建时调用
|
|
|
|
|
*
|
|
|
|
|
* @param db 可执行SQL的数据库对象
|
|
|
|
|
*/
|
|
|
|
|
public void createNoteTable(SQLiteDatabase db) {
|
|
|
|
|
// 执行创建笔记表的SQL语句
|
|
|
|
|
db.execSQL(CREATE_NOTE_TABLE_SQL);
|
|
|
|
|
|
|
|
|
|
// 重新创建与笔记表相关的触发器(确保触发器存在且最新)
|
|
|
|
|
reCreateNoteTableTriggers(db);
|
|
|
|
|
|
|
|
|
|
// 创建系统默认文件夹(如根目录、回收站等)
|
|
|
|
|
createSystemFolder(db);
|
|
|
|
|
|
|
|
|
|
// 记录操作日志
|
|
|
|
|
Log.d(TAG, "note table has been created");
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* 重新创建与笔记表相关的所有触发器
|
|
|
|
|
* 操作步骤:
|
|
|
|
|
* 1. 先删除所有已存在的触发器(避免重复创建或定义冲突)
|
|
|
|
|
* 2. 按正确顺序重新创建所有触发器
|
|
|
|
|
* 调用时机:
|
|
|
|
|
* - 在数据库创建时(onCreate)
|
|
|
|
|
* - 在数据库升级时(onUpgrade)
|
|
|
|
|
* - 当需要重置触发器逻辑时
|
|
|
|
|
*/
|
|
|
|
|
private void reCreateNoteTableTriggers(SQLiteDatabase db) {
|
|
|
|
|
// =====================
|
|
|
|
|
// 第一步:删除现有触发器
|
|
|
|
|
// =====================
|
|
|
|
|
|
|
|
|
|
// 删除更新父文件夹时的计数触发器
|
|
|
|
|
db.execSQL("DROP TRIGGER IF EXISTS increase_folder_count_on_update");
|
|
|
|
|
db.execSQL("DROP TRIGGER IF EXISTS decrease_folder_count_on_update");
|
|
|
|
|
|
|
|
|
|
// 删除删除笔记时的计数触发器
|
|
|
|
|
db.execSQL("DROP TRIGGER IF EXISTS decrease_folder_count_on_delete");
|
|
|
|
|
|
|
|
|
|
// 删除笔记时的级联删除触发器
|
|
|
|
|
db.execSQL("DROP TRIGGER IF EXISTS delete_data_on_delete");
|
|
|
|
|
|
|
|
|
|
// 插入笔记时的计数触发器
|
|
|
|
|
db.execSQL("DROP TRIGGER IF EXISTS increase_folder_count_on_insert");
|
|
|
|
|
|
|
|
|
|
// 删除文件夹时的级联删除触发器
|
|
|
|
|
db.execSQL("DROP TRIGGER IF EXISTS folder_delete_notes_on_delete");
|
|
|
|
|
|
|
|
|
|
// 移动文件夹到回收站时的级联移动触发器
|
|
|
|
|
db.execSQL("DROP TRIGGER IF EXISTS folder_move_notes_on_trash");
|
|
|
|
|
|
|
|
|
|
// =====================
|
|
|
|
|
// 第二步:重新创建触发器
|
|
|
|
|
// =====================
|
|
|
|
|
|
|
|
|
|
// 插入/更新/删除笔记时维护文件夹计数
|
|
|
|
|
db.execSQL(NOTE_INCREASE_FOLDER_COUNT_ON_UPDATE_TRIGGER);
|
|
|
|
|
db.execSQL(NOTE_DECREASE_FOLDER_COUNT_ON_UPDATE_TRIGGER);
|
|
|
|
|
db.execSQL(NOTE_DECREASE_FOLDER_COUNT_ON_DELETE_TRIGGER);
|
|
|
|
|
db.execSQL(NOTE_INCREASE_FOLDER_COUNT_ON_INSERT_TRIGGER);
|
|
|
|
|
|
|
|
|
|
// 级联删除逻辑
|
|
|
|
|
db.execSQL(NOTE_DELETE_DATA_ON_DELETE_TRIGGER); // 删除笔记时删除关联数据
|
|
|
|
|
db.execSQL(FOLDER_DELETE_NOTES_ON_DELETE_TRIGGER); // 删除文件夹时删除子笔记
|
|
|
|
|
|
|
|
|
|
// 回收站相关触发器
|
|
|
|
|
db.execSQL(FOLDER_MOVE_NOTES_ON_TRASH_TRIGGER); // 移动文件夹到回收站时级联移动子项
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* 创建系统必要的文件夹
|
|
|
|
|
* 这些文件夹是应用正常运行的基础,包含根目录、回收站等特殊文件夹
|
|
|
|
|
* 特点:
|
|
|
|
|
* - 均为系统类型(TYPE_SYSTEM),通常不显示给用户
|
|
|
|
|
* - 使用固定ID值,确保应用内引用一致性
|
|
|
|
|
* 调用时机:
|
|
|
|
|
* - 在数据库创建时(onCreate)
|
|
|
|
|
* - 在数据库升级需要重置系统文件夹时
|
|
|
|
|
*/
|
|
|
|
|
private void createSystemFolder(SQLiteDatabase db) {
|
|
|
|
|
ContentValues values = new ContentValues();
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* 创建通话记录文件夹
|
|
|
|
|
* 用途:存储通话相关的笔记
|
|
|
|
|
* 特殊属性:
|
|
|
|
|
* - ID固定为Notes.ID_CALL_RECORD_FOLDER
|
|
|
|
|
* - 类型为系统文件夹(TYPE_SYSTEM)
|
|
|
|
|
*/
|
|
|
|
|
values.put(NoteColumns.ID, Notes.ID_CALL_RECORD_FOLDER);
|
|
|
|
|
values.put(NoteColumns.TYPE, Notes.TYPE_SYSTEM);
|
|
|
|
|
db.insert(TABLE.NOTE, null, values);
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* 创建根文件夹
|
|
|
|
|
* 用途:作为所有顶层文件夹和笔记的默认父级
|
|
|
|
|
* 特殊属性:
|
|
|
|
|
* - ID固定为Notes.ID_ROOT_FOLDER
|
|
|
|
|
* - 类型为系统文件夹(TYPE_SYSTEM)
|
|
|
|
|
* - 通常在UI中显示为"所有笔记"
|
|
|
|
|
*/
|
|
|
|
|
values.clear();
|
|
|
|
|
values.put(NoteColumns.ID, Notes.ID_ROOT_FOLDER);
|
|
|
|
|
values.put(NoteColumns.TYPE, Notes.TYPE_SYSTEM);
|
|
|
|
|
db.insert(TABLE.NOTE, null, values);
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* 创建临时文件夹
|
|
|
|
|
* 用途:在笔记移动操作中作为中间存储位置
|
|
|
|
|
* 特殊属性:
|
|
|
|
|
* - ID固定为Notes.ID_TEMPARAY_FOLDER
|
|
|
|
|
* - 类型为系统文件夹(TYPE_SYSTEM)
|
|
|
|
|
* - 通常不显示在UI中
|
|
|
|
|
*/
|
|
|
|
|
values.clear();
|
|
|
|
|
values.put(NoteColumns.ID, Notes.ID_TEMPARAY_FOLDER);
|
|
|
|
|
values.put(NoteColumns.TYPE, Notes.TYPE_SYSTEM);
|
|
|
|
|
db.insert(TABLE.NOTE, null, values);
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* 创建回收站文件夹
|
|
|
|
|
* 用途:存储已删除的笔记和文件夹
|
|
|
|
|
* 特殊属性:
|
|
|
|
|
* - ID固定为Notes.ID_TRASH_FOLER
|
|
|
|
|
* - 类型为系统文件夹(TYPE_SYSTEM)
|
|
|
|
|
* - 通常在UI中显示为"回收站"或"已删除"
|
|
|
|
|
*/
|
|
|
|
|
values.clear();
|
|
|
|
|
values.put(NoteColumns.ID, Notes.ID_TRASH_FOLER);
|
|
|
|
|
values.put(NoteColumns.TYPE, Notes.TYPE_SYSTEM);
|
|
|
|
|
db.insert(TABLE.NOTE, null, values);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* 创建附件数据表并初始化相关触发器和索引
|
|
|
|
|
* 表结构:存储笔记的附件数据(如文本内容、图片、音频等)
|
|
|
|
|
* 执行流程:
|
|
|
|
|
* 1. 创建数据表结构
|
|
|
|
|
* 2. 重建相关触发器(确保数据一致性)
|
|
|
|
|
* 3. 创建必要的索引(加速查询)
|
|
|
|
|
*
|
|
|
|
|
* @param db 可执行SQL的数据库对象
|
|
|
|
|
*/
|
|
|
|
|
public void createDataTable(SQLiteDatabase db) {
|
|
|
|
|
// 执行创建数据表的SQL语句
|
|
|
|
|
db.execSQL(CREATE_DATA_TABLE_SQL);
|
|
|
|
|
|
|
|
|
|
// 重新创建与数据表相关的触发器(确保触发器逻辑最新)
|
|
|
|
|
reCreateDataTableTriggers(db);
|
|
|
|
|
|
|
|
|
|
// 为DATA表的NOTE_ID字段创建索引(加速查询笔记关联的数据)
|
|
|
|
|
db.execSQL(CREATE_DATA_NOTE_ID_INDEX_SQL);
|
|
|
|
|
|
|
|
|
|
// 记录操作日志
|
|
|
|
|
Log.d(TAG, "data table has been created");
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* 重新创建与附件数据表相关的所有触发器
|
|
|
|
|
* 操作步骤:
|
|
|
|
|
* 1. 删除已存在的触发器(避免重复创建或定义冲突)
|
|
|
|
|
* 2. 按正确顺序重新创建触发器
|
|
|
|
|
* 触发器功能:维护主表(note)的SNIPPET字段与附件表(data)的CONTENT字段同步
|
|
|
|
|
*/
|
|
|
|
|
private void reCreateDataTableTriggers(SQLiteDatabase db) {
|
|
|
|
|
// 删除现有触发器
|
|
|
|
|
db.execSQL("DROP TRIGGER IF EXISTS update_note_content_on_insert");
|
|
|
|
|
db.execSQL("DROP TRIGGER IF EXISTS update_note_content_on_update");
|
|
|
|
|
db.execSQL("DROP TRIGGER IF EXISTS update_note_content_on_delete");
|
|
|
|
|
|
|
|
|
|
// 重新创建触发器:
|
|
|
|
|
// 1. 插入文本数据时更新主表摘要
|
|
|
|
|
db.execSQL(DATA_UPDATE_NOTE_CONTENT_ON_INSERT_TRIGGER);
|
|
|
|
|
// 2. 更新文本数据时同步主表摘要
|
|
|
|
|
db.execSQL(DATA_UPDATE_NOTE_CONTENT_ON_UPDATE_TRIGGER);
|
|
|
|
|
// 3. 删除文本数据时清空主表摘要
|
|
|
|
|
db.execSQL(DATA_UPDATE_NOTE_CONTENT_ON_DELETE_TRIGGER);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* 获取数据库帮助类的单例实例
|
|
|
|
|
* 实现线程安全的懒汉式单例模式
|
|
|
|
|
* 特点:
|
|
|
|
|
* - 使用synchronized确保多线程环境下实例唯一
|
|
|
|
|
* - 使用static synchronized方法保证类级锁
|
|
|
|
|
*
|
|
|
|
|
* @param context 应用上下文
|
|
|
|
|
* @return 数据库帮助类的单例实例
|
|
|
|
|
*/
|
|
|
|
|
static synchronized NotesDatabaseHelper getInstance(Context context) {
|
|
|
|
|
// 双重检查锁定,确保只在实例未创建时进行同步操作
|
|
|
|
|
if (mInstance == null) {
|
|
|
|
|
// 使用应用级上下文避免内存泄漏
|
|
|
|
|
mInstance = new NotesDatabaseHelper(context.getApplicationContext());
|
|
|
|
|
}
|
|
|
|
|
return mInstance;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
@Override
|
|
|
|
|
/**
|
|
|
|
|
* 数据库首次创建时调用
|
|
|
|
|
* 执行流程:
|
|
|
|
|
* 1. 创建笔记主表(包含系统文件夹)
|
|
|
|
|
* 2. 创建附件数据表
|
|
|
|
|
* 注意:
|
|
|
|
|
* - 此方法在事务中自动执行(由SQLiteOpenHelper保证)
|
|
|
|
|
* - 触发器会在表创建时自动重建(通过createNoteTable和createDataTable内部调用)
|
|
|
|
|
*/
|
|
|
|
|
@Override
|
|
|
|
|
public void onCreate(SQLiteDatabase db) {
|
|
|
|
|
// 创建笔记主表及系统文件夹
|
|
|
|
|
createNoteTable(db);
|
|
|
|
|
|
|
|
|
|
// 创建附件数据表及相关触发器
|
|
|
|
|
createDataTable(db);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
@Override
|
|
|
|
|
/**
|
|
|
|
|
* 数据库版本升级时调用
|
|
|
|
|
* 执行流程:
|
|
|
|
|
* 1. 根据当前版本和目标版本执行逐步升级
|
|
|
|
|
* 2. 必要时重建触发器(确保触发器逻辑与新版本一致)
|
|
|
|
|
* 3. 验证最终版本是否符合预期
|
|
|
|
|
*
|
|
|
|
|
* @param db 可执行SQL的数据库对象
|
|
|
|
|
* @param oldVersion 当前数据库版本
|
|
|
|
|
* @param newVersion 目标数据库版本
|
|
|
|
|
*/
|
|
|
|
|
@Override
|
|
|
|
|
public void onUpgrade(SQLiteDatabase db, int oldVersion, int newVersion) {
|
|
|
|
|
boolean reCreateTriggers = false; // 是否需要重建触发器
|
|
|
|
|
boolean skipV2 = false; // 是否跳过v2升级步骤
|
|
|
|
|
|
|
|
|
|
// 版本1 -> 版本2升级(示例:添加新字段)
|
|
|
|
|
if (oldVersion == 1) {
|
|
|
|
|
upgradeToV2(db);
|
|
|
|
|
skipV2 = true; // 若从v1直接升级到v3或更高,跳过v2的单独升级
|
|
|
|
|
oldVersion++;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
// 版本2 -> 版本3升级(示例:修改表结构,需重建触发器)
|
|
|
|
|
if (oldVersion == 2 && !skipV2) {
|
|
|
|
|
upgradeToV3(db);
|
|
|
|
|
reCreateTriggers = true; // 标记需要重建触发器
|
|
|
|
|
oldVersion++;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
// 版本3 -> 版本4升级(示例:添加新索引或触发器)
|
|
|
|
|
if (oldVersion == 3) {
|
|
|
|
|
upgradeToV4(db);
|
|
|
|
|
oldVersion++;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
// 若升级过程中修改了表结构,重建所有触发器
|
|
|
|
|
if (reCreateTriggers) {
|
|
|
|
|
reCreateNoteTableTriggers(db); // 重建笔记表相关触发器
|
|
|
|
|
reCreateDataTableTriggers(db); // 重建数据表相关触发器
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
// 验证升级后的版本是否与目标版本一致
|
|
|
|
|
if (oldVersion != newVersion) {
|
|
|
|
|
throw new IllegalStateException("Upgrade notes database to version " + newVersion
|
|
|
|
|
+ " fails");
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* 从版本1升级到版本2(示例:表结构重构)
|
|
|
|
|
* 操作说明:
|
|
|
|
|
* - 由于V1表结构设计存在重大缺陷,选择删除旧表并重建
|
|
|
|
|
* - 重建后的数据表结构更优化(如新增字段、调整字段类型)
|
|
|
|
|
* - 会导致旧数据丢失,仅适用于开发阶段或测试环境
|
|
|
|
|
*
|
|
|
|
|
* @param db 可执行SQL的数据库对象
|
|
|
|
|
*/
|
|
|
|
|
private void upgradeToV2(SQLiteDatabase db) {
|
|
|
|
|
// 删除旧版本的表(V1表结构存在问题,需完全重建)
|
|
|
|
|
db.execSQL("DROP TABLE IF EXISTS " + TABLE.NOTE);
|
|
|
|
|
db.execSQL("DROP TABLE IF EXISTS " + TABLE.DATA);
|
|
|
|
|
|
|
|
|
|
// 重新创建表结构(基于V2设计)
|
|
|
|
|
createNoteTable(db);
|
|
|
|
|
createDataTable(db);
|
|
|
|
|
|
|
|
|
|
// 注意:此升级方式会导致数据丢失,生产环境应避免使用
|
|
|
|
|
// 正确做法:通过ALTER TABLE逐步修改表结构并迁移数据
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* 从版本2升级到版本3(示例:新增功能字段和系统文件夹)
|
|
|
|
|
* 操作说明:
|
|
|
|
|
* 1. 删除不再使用的触发器(清理旧逻辑)
|
|
|
|
|
* 2. 添加Google Tasks集成字段(GTASK_ID)
|
|
|
|
|
* 3. 新增回收站系统文件夹(支持数据恢复功能)
|
|
|
|
|
*
|
|
|
|
|
* @param db 可执行SQL的数据库对象
|
|
|
|
|
*/
|
|
|
|
|
private void upgradeToV3(SQLiteDatabase db) {
|
|
|
|
|
// =====================
|
|
|
|
|
// 步骤1:清理旧触发器(不再使用的修改时间触发器)
|
|
|
|
|
// =====================
|
|
|
|
|
db.execSQL("DROP TRIGGER IF EXISTS update_note_modified_date_on_insert");
|
|
|
|
|
db.execSQL("DROP TRIGGER IF EXISTS update_note_modified_date_on_delete");
|
|
|
|
|
db.execSQL("DROP TRIGGER IF EXISTS update_note_modified_date_on_update");
|
|
|
|
|
|
|
|
|
|
// =====================
|
|
|
|
|
// 步骤2:添加新字段(支持Google Tasks同步)
|
|
|
|
|
// =====================
|
|
|
|
|
db.execSQL("ALTER TABLE " + TABLE.NOTE + " ADD COLUMN " + NoteColumns.GTASK_ID +
|
|
|
|
|
" TEXT NOT NULL DEFAULT ''"); // 默认空字符串,避免NULL值
|
|
|
|
|
|
|
|
|
|
// =====================
|
|
|
|
|
// 步骤3:创建回收站文件夹(系统级功能)
|
|
|
|
|
// =====================
|
|
|
|
|
ContentValues values = new ContentValues();
|
|
|
|
|
values.put(NoteColumns.ID, Notes.ID_TRASH_FOLER); // 固定ID标识回收站
|
|
|
|
|
values.put(NoteColumns.TYPE, Notes.TYPE_SYSTEM); // 标记为系统文件夹
|
|
|
|
|
db.insert(TABLE.NOTE, null, values); // 插入系统表
|
|
|
|
|
|
|
|
|
|
// 补充说明:
|
|
|
|
|
// - 回收站文件夹用于存储删除的笔记,后续需配合触发器实现移动逻辑
|
|
|
|
|
// - GTASK_ID字段用于存储与Google Tasks同步的任务ID
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* 从版本3升级到版本4(示例:添加数据版本控制字段)
|
|
|
|
|
* 操作说明:
|
|
|
|
|
* - 添加VERSION字段用于数据冲突检测(乐观锁机制)
|
|
|
|
|
* - 默认值设为0,后续更新时通过触发器或业务逻辑递增
|
|
|
|
|
*
|
|
|
|
|
* @param db 可执行SQL的数据库对象
|
|
|
|
|
*/
|
|
|
|
|
private void upgradeToV4(SQLiteDatabase db) {
|
|
|
|
|
db.execSQL("ALTER TABLE " + TABLE.NOTE + " ADD COLUMN " + NoteColumns.VERSION +
|
|
|
|
|
" INTEGER NOT NULL DEFAULT 0"); // 版本号初始值为0
|
|
|
|
|
|
|
|
|
|
// 应用场景:
|
|
|
|
|
// 当多个设备同时修改同一条笔记时,通过比较VERSION字段避免数据覆盖
|
|
|
|
|
// 更新时逻辑:
|
|
|
|
|
// UPDATE note SET content=? WHERE id=? AND version=old_version
|
|
|
|
|
// 成功后VERSION字段自增
|
|
|
|
|
}
|
|
|
|
|
}
|