Found a usage example for the sqlite ftp3, it is seems like the
specification can be a little more complicated then just the USING
FTS. Here are examples from the webpage:

  CREATE VIRTUAL TABLE t USING fts3;
  CREATE VIRTUAL TABLE t USING fts3();
  CREATE VIRTUAL TABLE t USING fts3(content);
  CREATE VIRTUAL TABLE t USING fts3(TOKENIZE simple);
  CREATE VIRTUAL TABLE t USING fts3(content, TOKENIZE simple);

where TOKENIZE simple is not a collumn, but an argument to the fts3
engine.

Examples from:

http://www.sqlite.org/cvstrac/wiki?p=FtsUsage


On Jan 7, 3:26 pm, Michael Bayer <[email protected]> wrote:
> for now I'd support this as Table(...., sqlite_using='fts3').
>
> On Jan 7, 2009, at 1:05 PM, Michael Trier wrote:
>
> > Hi,
>
> > On Wed, Jan 7, 2009 at 6:11 AM, sol <[email protected]> wrote:
>
> > I'm not an sqlite guru, so I can only point to relevant doc's:
>
> >http://www.sqlite.org/lang_createvtab.html
>
> > The format after USING is
>
> >   module-name (module-arg-list)
>
> > where the (module-arg-list) is optional.
>
> > I got fts3 working by letting sqlalchemy do its thing and then issue
> > explicit drop and create virtual table statements on the DB. I can
> > then use the match() filter and it seems fine.
>
> > It would be great to have a way to do this without having to manually
> > mod the db.
>
> > Yeah the syntax is just:
>
> > CREATE VIRTUAL TABLE tablename using FTS3 (...)
>
> > When I wrote the unit tests I just did the create sql manually using  
> > execute and then autoloaded from there. I'd like to see the support  
> > of the USING syntax.
>
> > --
> > Michael Trier
> >http://blog.michaeltrier.com/
> >http://thisweekindjango.com/
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to