Ordinary SQLite vs FTS3 Tables

I have some data that is already organized in an SQLite table for my app. When I wanted to implement search functionality to my app, I found that the Searchable Dictionary example uses a FTS3 virtual table. I've never work with FTS3 and I just want to know what the differences are. When they say that FTS3 "does not support column constraints and thus, cannot declare a primary key," does that mean I can't make a column a type (ie. text, integer, etc.)? How do I specify unique identifiers (id)? Should I manage/organize the data differently from an ordinary table? Is it meant to replace my original table if I want to implement search functionality with FTS3?

---

我正在研究这个同样的事情，并发现这篇博文可能会回答你的一些问题：http://blog.andresteingress.com/2011/09/30/android-quick-tip-using-sqlite-fts-tables / 希望能帮助到你。

链接地址: http://www.djcxy.com/p/19186.html

上一篇: 使用启用了FTS3的SQLite

下一篇: 普通的SQLite vs FTS3表