本網站需要 JavaScript。
探索
說明
登入
crtxcr
/
looqs
關注
1
加上星號
0
Fork
0
您已經 fork 過 looqs
程式碼
問題
合併請求
1
版本發布
Wiki
動態
496aefaa09
looqs
/
shared
/
migrations
/
3.sql
2 行
25 B
MySQL
原始文件
標準檢視
歷史記錄
Unescape
Escape
shared: migrations: Add 3.sql: Drop potentailly harmful trigger In [1] it's stated that "If the values "inserted" into the text columns as part of a 'delete' command are not the same as those currently stored within the table, the results may be unpredictable." It's to be assumed only inserting ftsid is unpredictable. We have no way for a proper delete because files are not immutable or may have been deleted. For now the index will contain entries for files that don't exist. They won't appear in search results as they won't be joined in the query. [1] https://www.sqlite.org/fts5.html#the_delete_command
2022-08-13 13:33:54 +02:00
DROP
trigger
content_ad
;
複製固定連結