Απαιτείται JavaScript για να εμφανιστεί αυτή η ιστοσελίδα.
Εξερεύνηση
Βοήθεια
Είσοδος
crtxcr
/
looqs
Παρακολούθηση
1
Αστέρι
0
Fork
0
Έχετε ήδη κάνει fork το looqs
Κώδικας
Ζητήματα
Pull Requests
1
Κυκλοφορίες
Wiki
Δραστηριότητα
a3cfb7ade1
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
;
Αντιγραφή Permalink