StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20177490
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-11-24T17:23:02.637
FavoriteCount
0
LastActivityDate
2013-11-24T17:23:02.637
LastEditDate
LastEditorUserId
0
OwnerUserId
1197775
ParentId
20176945
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Not an answer, just a test. First, reduce the data extracting keywords for each poem as they are saved: <pre><code>rails g resource Keyword word occurrences poem_id:integer rails db:migrate </code></pre> Then in your Poem model: <pre><code># add more words EXCLUDED_WORDS = %w( the a an so that this these those ) has_many :keywords before_save :set_keywords # { :some => 3, :word => 2, :another => 1} def keywords_hash(how_many = 5) words = Hash.new 0 poem_column.split.each do |word| words[word] += 1 if not word.in? EXCLUDED_WORDS end Hash[words.sort { |w, w1| w1 <=> w }.take(how_many)] end def set_keywords keywords_hash.each do | word, occurrences | keywords.create :word => word, :occurrences => occurrences end end </code></pre> In <code>Keyword</code> model: <pre><code>belongs_to :poem def self.poem_ids includes(:poem).map(&:poem_id) end def self.poems Poem.where(id: poem_ids) end </code></pre> Then when you have word to search for: <pre><code>keywords = Keyword.where(word: word) poems = keywords.poems poets = poems.poets </code></pre> To use this last part, you would need in <code>Poem</code> model: <pre><code>def self.poet_ids includes(:poet).map(&:poet_id) end def self.poets Poet.where(id: poet_ids) end </code></pre> As far as I see this way would require just 3 queries, no joins, so it seems to make sense. I will think in how to extend this way to search by the entire content.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POBest way to optimize query while searching string in big sentences
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USjuanpastas
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POBest way to optimize query while searching string in big sentences
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COthe only thing is database issue, as we have to store info of each words or else its really reduced time. thanks and cheers Again the Keywords table will have millions of data
 singulars
 PostPostId
 PO
 UserUserId
 USdevudilip
2. COSQLite full text search makes much more sense, in @LS_dev comment. I was about to suggest to switch to a more usual production DB and use full text search, like PostgreSQL and use `pg_search` gem.
 singulars
 PostPostId
 PO
 UserUserId
 USjuanpastas

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.