>Does DISQLite have its own implementation of FTS, so not using FTS2 at
>all?
DISQLite3 uses the original full text search modules, adapted to Delphi. Both
FTS1 and FTS2 are already compiled in, and can both be used by the same
application (like SQLiteSpy does).
>Does it use the same mechanism as FTS2 with virtual tables?
Yes.
>And have you compared speed and functionality to FTS2,
Speed is likely to be a little faster than external FTS2, resulting from
register calling conventions.
DISQLite3's embedded FTS features are identical to external FTS. Just today I
uploaded a new version which adds a Unicode Pascal tokenizer written in Delphi
which you can use out of the box or as a basis for your own customized
tokenizer (see demo).
>I guess what it comes down to is to know options available, however I
>think the FTS2 project is great and hopes that it continues to grow, as
>it can be used on all platforms.
FTS in DISQLite3 is cross-platform database file compatabile, just as the
entire library. However, if you use custom tokenizers, user functions or
collation sequences with your Delphi application you need to replicate them on
other platforms.
>I guess what might be a problem is that I would not be able to use
>DISQLite's FTS implementation in Python or .net for example, or would I?
No, this is not a problem. Database files created by DISQLite3 can be read and
modified by Python, .net, or any other SQLite3 compatible applications. If in
doubt, run some test with SQLiteSpy: It uses DISQLite3 as its build-in SQLite3
implementation.
Ralf
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
