I'm currently creating a /base method which can search blog posts (from Blog 4 Umbraco). It also needs to return some other data which is currently done with Linq to Umbraco. I can also search the blogs with by simply adding some where statements to my Linq to Umbraco queries, but is that recommended? I know I can also use Umbraco Examine for this. What should I use?
After the Umbraco BeNeLux meeting I saw Umbraco Examine can be used for a lot more than just searching. I know it's really fast, but is it faster than XSLT with the umbraco.config XML cached? I know this is a "the right tool for the job" question, but could it be that a UserControl which uses Umbraco Examine to display data is faster than an XSLT file?
If an Examine provider for LINQ to Umbraco comes out I'll probably replace it for a lot of things where I now use LINQ to Umbraco with the NodeDataProvider.
Generally speaking Lucene will kick the ass of most other ways which you can access data.
If you configure your index well and do a good query then you should be fine. Be aware you'll loose performance if you start doing generic searching (ie - really loose term sets) or you use lots of wildcards. But if you're using it as a replacement for the Node API then you should be fine ;).
I am using examine regularly to do things like latest news on home page, current site i am working has quite a few articles in news section so to get the latest 3 to display on home page using examine is alot quicker than using xslt.
Search with L2U or Examine
Hello,
I'm currently creating a /base method which can search blog posts (from Blog 4 Umbraco). It also needs to return some other data which is currently done with Linq to Umbraco. I can also search the blogs with by simply adding some where statements to my Linq to Umbraco queries, but is that recommended? I know I can also use Umbraco Examine for this. What should I use?
Jeroen
I'm using Examine, because Examine is made for this stuff :-)
I've decided to use Umbraco Examine and it works perfectly :).
Jeroen
Sorry to hijack this thread, Examine is giving me a little grief.
Can either of you have a look here http://our.umbraco.org/forum/developers/extending-umbraco/13799-Examine-issues and confirm that you don't have these issues?
Cheers
Rich
Someone really should write an Examine provider for LINQ to Umbraco :P
@slace do it son we are with you all the way ;-}
Regards
Ismail
Using Linq with Examine sounds really great!
Jeroen
It's on my list, but it's a very long list of things to do :P
After the Umbraco BeNeLux meeting I saw Umbraco Examine can be used for a lot more than just searching. I know it's really fast, but is it faster than XSLT with the umbraco.config XML cached? I know this is a "the right tool for the job" question, but could it be that a UserControl which uses Umbraco Examine to display data is faster than an XSLT file?
If an Examine provider for LINQ to Umbraco comes out I'll probably replace it for a lot of things where I now use LINQ to Umbraco with the NodeDataProvider.
Jeroen
Generally speaking Lucene will kick the ass of most other ways which you can access data.
If you configure your index well and do a good query then you should be fine. Be aware you'll loose performance if you start doing generic searching (ie - really loose term sets) or you use lots of wildcards. But if you're using it as a replacement for the Node API then you should be fine ;).
Jeroen,
I am using examine regularly to do things like latest news on home page, current site i am working has quite a few articles in news section so to get the latest 3 to display on home page using examine is alot quicker than using xslt.
Regards
Ismail
When I was at The FARM we built a site which had half of a site running out of Examine ;)
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.