looqs/shared/migrations/migrations.qrc

<RCC>
    <qresource prefix="/looqs-migrations">
        <file>1.sql</file>
        <file>2.sql</file>
        <file>3.sql</file>
        <file>4.sql</file>
        <file>5.sql</file>
        <file>6.sql</file>
    </qresource>
</RCC>
shared: Begin db migration logic Issue: #26 2022-02-27 23:37:22 +01:00			`<RCC>`
			`<qresource prefix="/looqs-migrations">`
			`<file>1.sql</file>`
shared: migrations: Add 2.sql: Change to contentless FTS We never used the content copy we stored. It only wasted space. Update scheme so we do not store the content anymore. Switch to contentless FTS approach 2022-07-28 13:44:41 +02:00			`<file>2.sql</file>`
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			`<file>3.sql</file>`
shared: migrations: Add 4.sql: Begin trigram index 2022-10-18 16:04:00 +02:00			`<file>4.sql</file>`
migrations: Add 5.sql: Tag support 2023-04-02 21:37:30 +02:00			`<file>5.sql</file>`
migrations: Add 6.sql: Begin outline index 2023-05-14 14:05:26 +02:00			`<file>6.sql</file>`
shared: Begin db migration logic Issue: #26 2022-02-27 23:37:22 +01:00			`</qresource>`
			`</RCC>`