After reading a lot around and receiving a hint about SQL data normalization I came with this schema. The rest will be handled by simple requests:
Table MRindex - All details about a entry will be listed here: key db | user_made_id | description | date | blob_picture | rss_feed | twitter_alias/keyword/hashtag |
Table MRtwitter - All twitter related data will be stored here: key db| index-at-table1| tw_option|tw_user | tw_date | tw_location | tw_name |tw_text
Table MRrss - All rss data will be stored here: key db | index-at-table1| rss_post_author | rss_post_date | rss_post_title | rss_post_text
Any comments & hints would be more than welcomed :-)
EDIT: To clarify a bit...
MRIndex (also referred as table1) holds basic data, filled by the user: Might be user tweets, hashtags or location based tweets. Once this entry is filled up
MRtwitter will hold the tweets and related info. The field index-at-table1 is the "link" to table MRindex.
MRrss it's the the same for blog posts. Same thing applies for 'index-at-table1'.
For MRindex:
description: short user description
date: date of creation
blob_picture: a picture if any (jpg, png, etc)
rss_feed: An RSS_feed URL belonging to this user
twitter_alias/keyword/hashtag: either @user, Greece (for location) or #hashtag
Note that enabling FTS3 also makes FTS4 available. There is not a
separate SQLITE_ENABLE_FTS4 compile-time option. A build of SQLite
either supports both FTS3 and FTS4 or it supports neither.
Best Answer
The
sqlite3
command-line tool has the.output
setting.