The search feature is working, let me know if you think I should format it differently (ie adding some of the blog text into the search result, which I'll probably do). Also I need to add a message if the item isn't found, but I don't have time since I have to get ready for Bucca.
This is a boolean search feature that's more complex then the one TWG uses at the moment it's supposed to order everything by relevance but I don't know how the database determines these things. Â Right now it just lists things by when they were posted so I assume it's using posted date as part of the relevance.
here's a list of the boolean options
None By default (when neither + nor - is specified) the word is optional, but the rows that contain it are rated higher. This mimics the behavior of MATCH() ... AGAINST() without the IN BOOLEAN MODE modifier.
+ A leading plus sign indicates that this word must be present in every row returned.
- A leading minus sign indicates that this word must not be present in any row returned.
> < These two operators are used to change a word's contribution to the relevance value that is assigned to a row. The > operator increases the contribution and the < operator decreases it. See the example below.
( ) Parentheses are used to group words into subexpressions. Parenthesized groups can be nested.
~ A leading tilde acts as a negation operator, causing the word's contribution to the row relevance to be negative. It's useful for marking noise words. A row that contains such a word is rated lower than others, but is not excluded altogether, as it would be with the - operator.
" A phrase that is enclosed within double quote ('"') characters matches only rows that contain the phrase literally, as it was typed. The full-text engine splits the phrase into words, performs a search in the FULLTEXT index for the words. Before MySQL 5.0.3, the engine then performs a substring search for the phrase in the records that are found, so the match must include non-word characters in the phrase. As of MySQL 5.0.3, non-word characters need not be matched exactly: Phrase searching requires only that matches contain exactly the same words as the phrase and in the same order. For example, "test phrase" matches "test, phrase" as of MySQL 5.0.3, but not before.
