MobileRead Forums - View Single Post

un_pogaz · 09-10-2023, 02:17 AM

Okay.
So why create this merged DB directly? Why not add the 'main table' to the main DB and create a 'full text search db' separately? Any particular interaction? Or is just a non-final implementation?
I'm wondering because I'm synchronizing a backup of my library with exclusion of full-text-search.db

One idea that comes to mind is that you're planning to have massive "wikipedia biography" size notes, and so yes, it could be relevant to physically put them apart.

Also, is it normal for the 'full text search' annotation tables to be in the main DB, or is this an artifact of my testing with the indev code?

09-10-2023, 02:17 AM	#3
un_pogaz Chalut o/ Posts: 446 Karma: 672378 Join Date: Dec 2017 Device: Kobo	Okay. So why create this merged DB directly? Why not add the 'main table' to the main DB and create a 'full text search db' separately? Any particular interaction? Or is just a non-final implementation? I'm wondering because I'm synchronizing a backup of my library with exclusion of full-text-search.db One idea that comes to mind is that you're planning to have massive "wikipedia biography" size notes, and so yes, it could be relevant to physically put them apart. Also, is it normal for the 'full text search' annotation tables to be in the main DB, or is this an artifact of my testing with the indev code? Last edited by un_pogaz; 09-10-2023 at 02:39 AM.