tag:blogger.com,1999:blog-385473814989421290.post3713984271470453318..comments2017-12-12T12:23:48.029+00:00Comments on Morts Like Us: From The Book of Ideas: Searchable ActiveRecord-EntitiesAnonymoushttp://www.blogger.com/profile/06590048937018839085noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-385473814989421290.post-70482290698790735162007-11-07T08:53:00.000+00:002007-11-07T08:53:00.000+00:00@DariusHere is the user need:I have users here loo...@Darius<BR/><BR/>Here is the user need:<BR/><BR/>I have users here looking at a list of 200+ entities of a type. I built in some filters to narrow that down, but in interviews I perceived that they don't want any filter forms, but "simply" searching through a single text field. It turns out that such a search functionality will be needed on 10+ types for my current application, so I need some generic solution.<BR/><BR/>Attribute Usage:<BR/>Even when specifying graph depth, I will have way to many properties to include them all in a generic search. Some of my entities have 20+ properties, if I including only one relation level, I come to 50+. I don't want to put 50 disjunctions in a single query because I fear that it kills my DBMS.<BR/><BR/>Please do not forget that this functionality is additional to other, specific filters. It is mainly a "type and go" requirement of lazy users.<BR/><BR/>-MarkusAnonymoushttps://www.blogger.com/profile/06590048937018839085noreply@blogger.comtag:blogger.com,1999:blog-385473814989421290.post-84270999445380402842007-11-06T20:14:00.000+00:002007-11-06T20:14:00.000+00:00The idea is logical, but, i don't get what is the ...The idea is logical, but, i don't get what is the idea of having to put a searchable attribute?<BR/><BR/>Do you have a requirement that a search must be made only on some specific properties?<BR/><BR/>Basically, what I say is that maybe users will want to search through all properties in all cases, and thus that attributed is rendered redundant, we could simply take all castle property and relation attributes and add that to criteria.<BR/><BR/>Of course, this way we run into problem that if object graph is too deep, the query gets very big. Probably this might be avoided by specifying object graph depth value when constructing search criteria. <BR/><BR/>The idea is good, but i wonder what are the exact bussiness needs and use cases that drive this functionalityDarius Damalakashttps://www.blogger.com/profile/04596650719650364667noreply@blogger.com