Hello,




"George Ionescu" <[EMAIL PROTECTED]>
20/01/2004 05:25 PM

 
        To:     <[EMAIL PROTECTED]>
        cc: 
        Subject:        [sqlite] [Repost] Implementing Full Text Search


> The question is this: since most of RDBMS implement full text search, 
shouldn't this be a feature sqlite could support ?

Should this go into the FAQ?

The general answer to specific feature requests in the past has been "no". 
Sqlite is a "lite" sql. It's designed for embedded work with tight 
resources as much as it is for desktop platforms. If you, or a group of 
fellow developers/users, feel that such a feature could be useful to you I 
suggest that you don't wait around for approval from the group or DRH. I 
suggest that you keep the functionality you develop fairly modular so that 
it can be integrated with future versions of sqlite as they change, and I 
suggest that if you can come up with a few "elemental" or "enabling" 
features that could be used for other purposes too then you might request 
they be rolled back into the base product.

In this case I suppose an enabling feature might be a way to do indexing 
on transformed field data, or perhaps the ability to define an index with 
multiple entries per source table row. I'm guessing this would probably be 
necessary for a text search where the phrase "I have a cat" could be 
indexed as "I have", "have a", and "a cat". Presumably if you did an SQL 
query which used this index you would only want the row returned once, 
despite the mulitple index entries. On the other hand, if you could 
achieve the same thing just by adding extra tables to the database with 
their own indicies and using triggers the base sqlite may not require 
changes to support your work. Perhaps the best enabling enhancements would 
be a way of dividing up the database into the "normal" section and 
individual sections associated with specific pluggable functions. Each 
section could have its own namespace to avoid conflicts between user needs 
and the needs of the automatic infrastructure. I suspect that's how many 
of the bigger databases do things in the end, anyway. They code up a 
fundamental VM and then impliment all their "advanced" features as 
triggers and hidden tables and functions in the database.

Benjamin.



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to