Re: [sqlite] Registering a custom tokenizer per database rather than per connection

On Tue, Oct 12, 2010 at 8:40 AM, Drake Wilson wrote: > Just to clarify, a trigger isn't useful for this in general, because > you still have nowhere to get the function pointer from.  Above I was > worrying that the current SQLite code might be less safe than it could > be as a result of allowing

Re: [sqlite] Registering a custom tokenizer per database rather than per connection

Quoth Travis Orr , on 2010-10-12 08:17:38 -0700: > Drake Wilson said: > - However, it now occurs to me that it may be possible to use the > - fts3_tokenizer() function in a trigger, which is probably a bad thing > - when writing to untrusted databases. > > I suppose the only way to accomplish it

Re: [sqlite] Registering a custom tokenizer per database rather than per connection

-boun...@sqlite.org] On Behalf Of Drake Wilson Sent: October 8, 2010 9:02 PM To: General Discussion of SQLite Database Subject: Re: [sqlite] Registering a custom tokenizer per database rather than per connection Quoth Travis Orr , on 2010-10-08 13:37:25 -0700: > Is it possible to register a cus

Re: [sqlite] Registering a custom tokenizer per database rather than per connection

Quoth Travis Orr , on 2010-10-08 13:37:25 -0700: > Is it possible to register a custom FTS3 tokenizer to be persistent in > the database so that it is available every time a connection is opened? Not really. How would this work? You open a database, and the function pointer for the tokenizer com

[sqlite] Registering a custom tokenizer per database rather than per connection

Is it possible to register a custom FTS3 tokenizer to be persistent in the database so that it is available every time a connection is opened? Or do I need to reregister the tokenizer every time I open a new connection to the database? Thanks Travis Orr IVL Audio Inc #3-6703 Rajpur Pla