Even without having FTS1 loaded, can't you delete the *_content and *_term tables directly and that would be effectively the same as deleting the virtual table?
Sam ------------------------------------------- We're Hiring! Seeking a passionate developer to join our team building products. Position is in the Washington D.C. metro area. If interested contact [EMAIL PROTECTED] On 7/9/07, Scott Hess <[EMAIL PROTECTED]> wrote: > > If you have not compiled in fts1, and try to drop an fts1 table, > you'll get an error. I don't think you'll get a crash, but sqlite > will simply not know how to deal with the table. > > I can think of two ways to deal with this. When builidng a new > version, you could just leave the fts1 code in place. Otherwise, you > could put the fts1 table in an attached database, which you could > delete using filesystem operations when you upgrade. > > I would recommend just having both fts1 and fts2 available. If you're > super-concerned about code size, you could pretty easily strip out all > of the interesting code from fts1.c and leave only enough to > successfully drop tables. A little more aggressive would be to leave > enough code to do read-only queries without the fulltext index (useful > for pulling all the content data across to fts2). > > [Let me know if I misread your question.] > > -scott ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
