as i learned theses days loadallpaged procedure does all product search for nop. It is working with MS "Contains". That means we don't get hits for sample product "TestBrand TestMake 120" if we type in "TestBrand Make" or "TestMake" or "Brand Testmake 120". This is kind of annoying for users. So i would like to replace
@sql = @sql + 'OR CONTAINS(p.[Name], @Keywords) '
with something like
@sql = @sql + 'AND p.[Name] 1 like '%' + @Splitkeypart1 +'% AND p.[Name] 1 like '%' + @Splitkeypart2+'%' and so on ...
Has anyone successfully done this modification for loadallpaged procedure or anything with similar effect?
All hints welcome!
Are you using SQL Server full-text search?
Hm. Hitting "Abcdoor" when typing in "door" is basic search engine stuff imho.
Product tags have no effect on search output.
Did i get that right (@noptools): Suggestion is to add an - OR - Statement to loadallpages procedure which uses a "Contains[@Keywords, ...] backward" statement to fix this?
Thanks for sharing this.
RE: 'Hitting "Abcdoor" when typing in "door" is basic search engine stuff imho.
Contains/Full-text search is based on words/phrases (versus LIKE which uses 'pattern')
RE: "Product tags have no effect on search output."
@SearchProductTags is a param to the stored procedure. I don't recall how/when it's used. (You can look at the source code ;)
RE: Suggestion is to add an - OR - Statement...
Yes, the idea is to use both Contains/Full-text and the LIKE (pattern).
It will impact your performance if you have many products.