zadam/trilium
1
1
Fork 0
mirror of https://github.com/zadam/trilium.git synced 2025-02-20 21:13:11 +08:00
Code Issues Projects Releases Packages Wiki Activity

fix setting isErased after note migration

Browse source
This commit is contained in:
zadam 2019-11-11 23:37:46 +01:00
parent 4ba7e74b58
commit 7bd1d8feb4
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
db/migrations/0151__add_isErased_to_note.sql
View file

@ -20,7 +20,7 @@ DROP TABLE notes;
ALTER TABLE notes_mig RENAME TO notes;
UPDATE notes SET isErased = 1 WHERE isDeleted = 1
AND (SELECT CASE content WHEN NULL THEN 1 ELSE 0 END FROM note_contents WHERE note_contents.noteId = notes.noteId);
AND 1=(SELECT CASE content WHEN NULL THEN 1 ELSE 0 END FROM note_contents WHERE note_contents.noteId = notes.noteId);
CREATE INDEX `IDX_notes_isDeleted` ON `notes` (`isDeleted`);
CREATE INDEX `IDX_notes_title` ON `notes` (`title`);

2
src/services/consistency_checks.js
View file

@ -364,7 +364,7 @@ async function findLogicIssues() {
AND content IS NULL`,
async ({noteRevisionId}, autoFix) => {
if (autoFix) {
const noteRevision = await repository.getNote(noteRevisionId);
const noteRevision = await repository.getNoteRevision(noteRevisionId);
await noteRevision.setContent('');
logFix(`Note revision ${noteRevisionId} content was set to empty string since it was null even though it is not erased`);