Unfortunately, it appears to suffer from the same shortcomings as the dpcprints search. That is, it relies entirely on the FULLTEXT search capabilities provided by MySQL. Despite its convenience, it is impossible to search for words like "from", "above", "four", "third", "alone", along with over 500 others. The 4 character restriction imposed by MySQL is overly restrictive, especially for the small amount of data DPC is using. Searching for "dof" is impossible, although one can hope that "depth focus" will be good enough.
Unfortunately, it appears to suffer from the same shortcomings as the dpcprints search. That is, it relies entirely on the FULLTEXT search capabilities provided by MySQL. Despite its convenience, it is impossible to search for words like "from", "above", "four", "third", "alone", along with over 500 others. The 4 character restriction imposed by MySQL is overly restrictive, especially for the small amount of data DPC is using. Searching for "dof" is impossible, although one can hope that "depth focus" will be good enough.
I wonder how small a dataset it really is, given the amount of noise we've made in the last couple of years. I know it took several hours to index...
I wonder how small a dataset it really is, given the amount of noise we've made in the last couple of years. I know it took several hours to index...
The time to index is affected by other factors too, but in this case there are just over 100k posts (rows) and each post contains less than 1k bytes (and probably half that). It might not seem small to some, but in my experience it's fairly small.
That explains why my search for '10D' failed. Still, it's great to have a search. This has been needed for quite a while. Thank you thank you thank you.
Unfortunately, it appears to suffer from the same shortcomings as the dpcprints search. That is, it relies entirely on the FULLTEXT search capabilities provided by MySQL. Despite its convenience, it is impossible to search for words like "from", "above", "four", "third", "alone", along with over 500 others. The 4 character restriction imposed by MySQL is overly restrictive, especially for the small amount of data DPC is using. Searching for "dof" is impossible, although one can hope that "depth focus" will be good enough.
Indeed, and it's fueled more by the fact that we're still on an older version of MySQL, so boolean searches are not possible ("+camera -35mm", as well as use of and/or). In the event that we do upgrade, such a search will be available immediately.
Indeed, and it's fueled more by the fact that we're still on an older version of MySQL, so boolean searches are not possible ("+camera -35mm", as well as use of and/or). In the event that we do upgrade, such a search will be available immediately.
The boolean features of FULLTEXT seem like a moderate improvement. Certainly, people are already used to searching like this (the google effect). The stopword issue (and to a lesser extent the 4-char limitation) makes FULLTEXT for small data sets less useful, but it's especially bad on DPCprints where image titles/keywrods contain stopwords. People should know about that.
Anyway, it's certainly nice to have search, even if it comes with mysterious (generally undocumented) shortcomings.
For the older stuff, doesn't google already do a bang up job of indexing for you? And you get boolean & short word support and no mysql stopwords.
actually, that's a good point. ive pointed out a few times that, using the google toolbar, you get the ability to search within any website.
but maybe it's too hard to do (like setting the time on the VCR?) because, as far as I know, I'm the only person who does it. LOL.
The reason most people don't use it is probably a UI thing. People are used to being able to search a site through search methods provided by the site, not using a third party. Maybe we could do like other places I've seen and embed google into the page - I've seen this done
but I'm not sure of the costs associated with enabling this.
Maybe we could do like other places I've seen and embed google into the page - I've seen this done
but I'm not sure of the costs associated with enabling this.
