I had an API problem, and I now think that the virtual table does not need to be created each time. I can't find documentation that covers this.
The question on threading the virtual table construction still stands. If I don't have any response in a day or so I will close this issue. -------- Original Message -------- Subject: Fwd: fts virtual table questions Date: Mon, 28 Feb 2011 22:48:58 -0700 From: Paul Shaffer <sqli...@cyberplasm.com> To: General Discussion of SQLite Database <sqlite-users@sqlite.org> Edit: with doing a create virtual call --> without doing a create virtual call -------- Original Message -------- Subject: fts virtual table questions Date: Mon, 28 Feb 2011 22:46:32 -0700 From: Paul Shaffer <sqli...@cyberplasm.com> To: General Discussion of SQLite Database <sqlite-users@sqlite.org> I am still testing my results and am new to fts. To use fts, is "create virtual table" required every time my program runs and opens the sqlite database? I see that the table (plus a few other related fts tables) is physically present in the database after my program closes. I would prefer to not recreate this table every time I launch my windows forms application. I have tried to use the existing table with doing a create virtual call, but I get table not found exception. The table takes an additional 10 seconds or so to load at program start. If I have to create the virtual table every time my program runs, I will first resort to creating the table on a background thread. Do you know of any problems doing this aside from the usual threading concerns? How is this usually handled in desktop applications? _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
