Universal’s CEO Once Called iPod Users Thieves. Now He’s Giving Songs Away. unsurprising portrait of a music industry exec who’s technology ignorant, and rather proud of it. if i was a shareholder, i’d be appalled. (tags: sethmnookin universal riaa...
Selected links related to Semantic Web technologies for the week ending 2007-11-26, all weeks . Also available in RDF as linked data or via GRDDL . In the Media Podcast: @semantics and the Semantic Web Podcast: The Social and Semantic Webs Podcast:...
Perhaps you could consider using the SQLite amalgamation.
The amalgamation is a single large source code file that
contains the entire SQLite implementation, and (as of
version 3.5.3) the Full-text search engine. You have a
single file to compile (sqlite3.c) which contains everything
you need. If you compile this one file into whatever form
of library you need, and you use the -DSQLITE_ENABLE_FTS3=1
option, then you will end up with a version of SQLite that
contains full-text search built-in and which is therefore
usable from the DB-API or whatever interface wrapper
you normally use.
I did take a look at that, but it wasn’t documented in the README, didn’t look like it included the extensions (and now, looking at it again, only appears to declare and call extern int sqlite3Fts3Init).
Looking at the wiki and at the source, it isn’t obvious what is now supposed to work vs what was once thought to be promising and now has been discarded.
Meanwhile, I’ve exploring other areas — like discovering that the suggestions on how to join full text data make deletions “interesting” particularly given the aspects of SQL which are unsupported, and vacuuming downright dangerous.
But I’m making progress. In a day or two I should have something to show for it.